Code cleanup removing potential issues detected by FindBugs

Fix an issue with connection timeouts in CLI. The timeout is now configurable on CLI with the --connectTimeout option (expressed in milliseconds), the default is 30 000 milliseconds. This solves Issue 4196.

Fix for issue 4295 (Issues with dsreplication interactive mode) The following changes complete the previous fix done for this bug, if we were using dsreplication enable on the installation of one of the servers, the interactive mode failed if the option --trustAll was NOT specified.

Fix for issue 4160 (Connection issue with new dsreplication interactive mode)

Refactor the code of dsreplication and extract some of its commodity methods and move them to the classes they apply to. Fix a potential bug when enabling a replication topology using a replication server with no domains as one of the servers to be replicated.

Fix for issue 2017 (tools usage should disclose default value for options) The changes include the required modifications to set the default values of the configuration file in the arguments. The main modifications affect the classes LDAPConnectionConsoleInteraction and SecureConnectionCliArgs. Most of the code in charge of reading the configuration has been moved to SecureConnectionCliArgs in order the arguments to be updated with those default values before the arguments are actually parsed. This makes sense also since SecureConnectionCliArgs was already in charge of providing the trustmanager. LDAPConnectionConsoleInteraction depends on SecureConnectionCliArgs but the latter does not rely on the former, so this change does not have a negative impact in terms of dependencies.

Fix for issue #3625 : CLIs : Avoid certificate interaction in interactive mode This fix improves the ease of use of dsconfig and other CLIs: 1. If the CLI is launched in the same instance than the server, there is no anymore the user interaction for certificate checking. The truststore used is the one of the administration connector (which is always present). 2. The default port is the one of the local configuration file (instead of 4444). CLIs that will take benefit of this are : - dsconfig - status - dsreplication - manage-tasks - uninstall Note that this change does not break any interface: it just simplifies the user interaction in case of CLI and server running in the same instance (which is what we usually do). In non-interactive mode, in this case the "-X/--trustAll" is not required anymore (although it can still be used).

Add options displayCommand and commandFilePath to the dsreplication command-line. These options display the equivalent non-interactive command-line when dsreplication is run in interactive mode (they are the same options already provided by dsconfig). The WIKI content has already been updated to reflect these changes. Fix a bug that made some passwords passed in the command-line as file arguments to be ignored in interactive mode.

The commit will bring the following features : - An updated version of the underlying database. BDB JE 3.3 is now used. - Attribute API refactoring providing a better abstraction and offering improved performances. - A new GUI called the Control-Panel to replace the Status-Panel: the specifications for this GUI are available on OpenDS Wiki and contains a link to a mockup. See <https://www.opends.org/wiki/page/ControlPanelUISpecification>. - Some changes in the replication protocol to implement "Assured Replication Mode". The specifications are on OpenDS Wiki at <https://www.opends.org/wiki/page/AssuredMode> and section 7 described some of the replication changes required to support this. Assured Replication is not finished, but the main replication protocol changes to support it are done. As explained by Gilles on an email on the Dev mailing list (http://markmail.org/message/46rgo3meq3vriy4a), with these changes the newer versions of OpenDS may not be able to replicate with OpenDS 1.0 instances. - Support for Service Tags on the platforms where the functionality is available and enabled. Specifications are published at <https://www.opends.org/wiki/page/OpenDSServiceTagEnabled>. For more information on Service Tags see <http://wikis.sun.com/display/ServiceTag/Sun+Service+Tag+FAQ>. - The Admin Connector service. In order to provide agentry of the OpenDS server at any time, a new service has been added, dedicated to the administration, configuration and monitoring of the server. An overview of the Admin Connector service and it's use is available on the OpenDS wiki <https://www.opends.org/wiki/page/ManagingAdministrationTrafficToTheServer> - Updates to the various command line tools to support the Admin Connector service. - Some internal re-architecting of the server to put the foundation of future developments such as virtual directory services. The new NetworkGroups and WorkFlow internal services which have been specified in <https://www.opends.org/wiki/page/BasicOperationRoutingThroughNetworkGroup> are now implemented. - Many bug fixes... This set of changes may have an impact on current clients and deployments, however it should be possible to upgrade existing 1.0 instances. Some of the changes impacting the clients include : - Scripts using the command line tools including dsconfig will need to be updated (usually to remove some no longer required options).

Fix for issue 3516 (dsconfig --displayCommand issue) Only add the trustStorePassword parameter if the user actually provides it. Do not display the --advanced option in the equivalent command since it makes no sense in not-interactive mode.

Fix for issue 2197 (dsconfig: interactive mode should display the effective dsconfig command) After discussing with different members the following has been committed: * The current behavior is kept (no additional output by default). * Two new options have been added: --displayEquivalentCommand Display the equivalent non-interactive argument in the standard output when this command is run in interactive mode --equivalentCommandFilePath {path} The full path to the file where the equivalent non-interactive commands will be written when this command is run in interactive mode So the user will have to explicitly ask to display the equivalent command-line (or to dump it to a file). This approach privileges the users that configure the server using interactive dsconfig instead of those whose ultimate goal is to create scripts to configure the server (and to whom this feature is targetted). In terms of implementation basically what is done is to create a new class called CommandBuilder when we store the equivalent arguments to what the user provides interactively. When the user applies a change (or asks to display a list of objects) the equivalent command-line is displayed by using the contents stored in the CommandBuilder object.

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

Fix for issue 2214 (Provide a manner to accept permanently certificates). Change the labels of the Certificate Dialog and add a new button to be able to update the certificate permanently. The modifications only apply to graphical interface since the command-line utilities already allow the user to accept permanently the certificates. These modifications include also a fix in ApplicationTrustManager which did not parse properly the Subject DN of the certificate and reported systematically a host name mismatch.

Fix some issues in the interactive mode of dsreplication enable and dsreplication disable when the user provides values in the command-line.

Remove some unused methods. Fix a bug in the uninstall and dsreplication. When the user connected to the servers using LDAP, a null trust manager was used to load the topology (so all certificates were accepted). The code has been fixed to prompt the user to accept non trusted certificates.

Update the dsreplication command-line to be consistent with dsconfig in the use of menus and in the order that questions to connect to the servers. Update the upgrade to use the same menus as the other command-lines. Do some minor changes in the uninstall command-line in order to be more consistent with dsconfig in the order where the connection parameters are provided. Fix a bug in ApplicationTrustManager related to the accepted certificates when there is a mismatch between the certificate and the host name. Do some refactorization of the code and remove the CliApplicationHelper class so that we use ConsoleApplication everywhere.

Update the code of the interactive installer to be consistent with dsconfig, setup and status command-lines in the formatting and in the format used to present certificates to the user. Fix some bugs in the way the ADS was updated when an instance is uninstalled.

The following modifications are aimed to have the same interaction in the status and dsconfig command lines by sharing the same code. The formatting of the table in status command-line has also be modified to be consistent with the one provided by dsconfig.

Addresses issue 2338 in which manage-tasks signals an error if the user tries to use SSL connection options. The reason for the error is that LDAPConnectionArgumentParser does not properly support initialization of the LDAPConnectionOption's SSL connection factory. This change involves adding some state variables to LDAPConnectionConsoleInteraction that are populated during the session

With these modificationd, if both useSSL and useStartTls are set to false in the properties file, dsconfig interactive mode will not prompt for protocol.

Introduces a utility 'manage-tasks' for monitoring and some management of tasks called 'manage-tasks'. It can be used in either one-time or menu-driven execution mode to print a summary of task information, print verbose information about a particular task, or cancel a running or pending task. When starting the tool, 'manage-tasks' requires a connection to the directory to interact with the backend and prompts for information (unless given the -n/--no-prompt option) like 'dsconfig'

If the user specify a keystore, we will now prompt for certificate nickname found in the keystore.

Correct a number of misspelled occurrences of "StartTLS".

Fix for issue #2240

separated CLI code from context creation for reuse