Fix for OPENDJ-222 : More fixes, rebranded all temp files, some resources, fixed more messages...

Fixing several issues with the Control Panel, the QuickSetup, Core server and Replication. Also improves unit, functional tests. More specifically this commit resolves the following open issues: 4385 - NPE when using ExtensibleMatch filter without a matching rule 4521 - dynamic lookup in attribut selection when selecting the sort order attribut while defining VLV index 4531 - Control Panel creates virtual static groups using groupOfURLs as objectclass 4533 - NullPointerException when configuring replication between 2 OpenDS 4539 - DSML Gateway - jaxb.properties Exception

Fix a bunch of warnings mentioned by the IDE (most of them related to the non-use of generics).

Fixes * Update tools and properties files to use the DynamicConstants class definitions : Product Name, Short Name, Version etc ... * setup, uninstall, control-panel, upgrade. * Update the ID for ST registration for the coming milestone OpenDS 2.2 * Update the welcome screen to use the DynamicConstants class definitions . In particular update the documentation pointer and description. * Replace the link to the QuickReference Guide by the Administration Guide

svn merge -r5333:5417 https://opends.dev.java.net/svn/opends/branches/b2.0

Fix for issue 3854 (Uninstall fails on Windows (due to log files)) There are a bunch of issues here: 1. The server was not stopped after being started if it contains replicated data. 2. The log files do not contain enough information. New debug lines have been added. 3. One of the problems also found is that one of the remote servers to be updated (to remove the replication references) could not be contacted. This is the expected behavior if the option forceOnError is NOT specified. However the error message was not very clear about what was happening. The new error message is very explicit about this and informs the user of the existence and behavior of the forceOnError option.

Fix for issue 2972 (The usage of stop-ds.bat shows the class name) The fix consists on updating the scripts and the java code to reflect correctly the name of the script and be consistent with all the other batch files (we don not include the .bat on the usage). Apart from that the modifications include a modification in StatusPanelLauncher so that we use the ArgumentParser class in the whole class (this avoids duplicated code and fixes a bug with the usage).

Fix for issue 2960 (uninstall -? launches graphical interface) Instead of checking for the presence of the help argument call SubCommandArgumentParser.usageOrVersionDisplayed that actually takes into account the built-in option '?'.

Fix for issue 2918 (status and uninstall direct --help output to STDERR) Use the standard output to display the usage and update the return codes of the status-panel script.

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

Fix for issue 2582. Make the setup command line to support properties files. Make the uninstall command line to support properties files. Support properties files in dsreplication for all the subcommand arguments.

After some discussions it has been decided to merge the setup and uninstall commands so that we have the behavior that we had before. So with this changes, in order to work in CLI mode the option --cli must be specified.

Update the messages in admin_tool.properties to use the proper severity and not only the INFO severity. Add some methods in the SecureConnectionCliParser that will be used by the replication CLI utilities.

The following modifications have the following goals: 1. Provide a fix for the CLI part of issue 1894 (consider replication in uninstall). The command line now proposes to remove references in remote servers of the server that is being uninstalled. 2. Add options to specify to uninstall only some parts of the server as appears in http://bde.central.sun.com/projects/opendsw/cmdline/commandmatrix.html. 3. Fix some bugs in the messages. 4. The fix of 1894 includes some code to display certificates to the user so that they can be viewed and accepted interactively. 5. Separate the uninstall command-line into two different command lines (uninstall-gui and uninstall) as appears in http://bde.central.sun.com/projects/opendsw/cmdline/commandmatrix.html.

This commit is a step toward getting OpenDS internationalized. There are still issues to be resolved before we can declare that we are internationalized but this commit covers the bulk of changes needed at this time. In general this commit converts any string values that might potentially be shown to an end user (client or administrator) to a new class called Message. This includes exception messages, error log messages, alert and email text, labels, and CLI output. Message's main interface includes methods for rendering itself as a string in the default locale using toString() or a specified locale toString(Locale). In addition to addressing localization, this would allow us to potentially support controls allowing clients to set a preferred locale for server communication or output log messages in different languages. Message extends CharSequence so it can be used in some places where strings are currently used with not code change (e.g. writing to a buffer) as well as allowing messages to be composed of one another. In order to create localized messages, instead of adding them to the *Messages.java class, you define them in the corresponding properties files. In general the property file keys are used to derive the new messages severity, category, and ordinal. There are directives that can be used in the properties file in order to avoid doing this however. For instance all the properties files used internally include the 'global.category' directive at the top of the file that instructs the generator to make all the following message belong to a single category. So for internal messages the property value key will be as follows: [SEVERITY]_[DESCRIPTION]_[ORDINAL] See the properties files themselves for more information. Once your messages are in the properties file you can use the ant target 'generatemessages' to create create MessageDescriptor objects that are referred to in the Java code. In the code you might think of these objects as replacing the int-valued message IDs. To create messages you call MessageDescriptor.get() which replaces MessageHandler.getMessage(). It might be helpful then to try to define your messages before referring to them in your code since until you run 'generatemessages' you won't have any Java-code with with to create your message objects. In order to support non-localizable text in messages (host names, DN's, etc.) Message's can be created from String values by calling Message.raw(String). In this way it is also possible to circumvent the intention of changing the APIs to use Message objects instead of Strings which is to support writing of localizable messages. This method is currently used in the code as a crutch for areas of the code that need internationalization (tagged with a 'TODO: i18n' comment). It might also be used by 3rd party developers that don't intend to localize their products. However for internal use we should not be using this method to create Messages for text that is locale sensitive. Additionally this code includes a MessageBuilder that can be used in much the same way that a StringBuilder can be used. It has a method toMessage() that can be used to generate a message object when needed. At this time this method just converts the buffer contents to a raw, unlocalizable message so this will need to addressed in the future. Some other issues: - While all of the unit tests pass after this commit, there may be issues in the code where we have no or minimal test coverage. This includes much of the setup and GUI tools packages for which I have not done any testing but will begin after this commit. - The new message related Java sources are contained in package org.opends.messages and organized in a new module src/module modeled somewhat after the admin module: src/messages/src (non-generated Java source files) src/messages/generated (generated source files) src/messages/messages (properties files for messages) If you run the code from within your IDE you will have to mark all messages/src, messages/generated and messages as source directories. - To generated the MessageDescriptor files you invoke the 'generatemessages' target. - If you run the code from within your IDE you will probably ne - This commit would change the plugin API. Here are the changes caught by DirectoryServerPluginTestCase: doShutdown(String)->doShutdown(Message) doPostDisconnect(PostDisconnectPluginResult,ClientConnection,DisconnectReason,int,String) -> doPostDisconnect(PostDisconnectPluginResult,ClientConnection,DisconnectReason,Message); - This commit aligns the entire code-base behind the new Formatter class (printf style formattings like %s) as opposed to the older MessageFormat style (using curly braces for message arguments). This allows us to provide more type safety for message arguments. So for instance you can include a %c argument specifier in your format string and the MessageDescriptor will enforce specification of a Character as message creation time. - Not all of the config framework has not been converted to use Messages. Perhaps as some point we might have a 'message' syntax for locale-sensitive textural data. I'm sure Matt will have ideas about this. - In addition to Message, MessageDescriptor and MessageBuilder, the org.opends.server.message package includes enums for Category and Severity that replace the definitions formerly found in MessageHandler. - The interface for the ErrorLogger has been simplified to allow logging of messages using a single Message parameter. The severity and category of the message will be derived from the Message itself instead of specified as arguments when a message is logged. - I will provide more documentation about this plumbing on the Wiki shortly. - I will expand on the included tests soon.

Fix for issue 1857 (Uninstall silent option works as interactive option). The following modifications add a new option 'interactive' to the uninstall command line. The way interactive and silent work now in the uninstall command line is similar to the way the work for the upgrader.

The following modifications have the following goals: 1. Provide a fix for the GUI part of issue 1894 (consider replication in uninstall). Basically the graphical uninstall checks whether there is an ADS defined and if the server is configured for replication and asks the users whether (s)he wants to remove the references to the server that is being uninstalled. 2. Fix some minor issues that appear in the merged version of the installer and upgrader. 3. Update the build so that statuspanel.jar disappears. The idea is to minimize the number of jars that we have. This is a requirement coming from customers and approved by Neil in a conversation we had a while ago. 4. Minimize the number of classes that go to quicksetup.jar so that its size is the minimal possible and we reduce the download time when launching the WebStart based tools. This has been done by moving the uninstaller tool to OpenDS.jar (with the status tools).