23 Aug, 2007
7 commits
-
…AP connection that can be used to schedule these operations as tasks in addition to the current behavior of operating locally. - In order to add the LDAP connection arguments I changed the short identifier for the -h/--hash argument of back up to be -A - BooleanArgument was changed to have an implicit value equal to that of the value of isPresent() and a default value of "false". - Scheduling an ImportLDIF task now respects the quiet argument and does not print a confirmation message if present. git-svn-id: https://svn.forgerock.org/opendj/trunk@2757 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
…revious value is longer then the new value. If the previous value was set to a long time (ie 5 hours), the new value wouldn't take effect until the previous 5 hours has expired. With this fix, the new value will take effect immediately by interrupting the rotator thread if its asleep. Fix for issue 2103 git-svn-id: https://svn.forgerock.org/opendj/trunk@2755 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
…rd argument which is the number of spaces to indent each wrapped line. There are also delegate wrapText() methods which simulate the old behavior by passing an indentation of 0. git-svn-id: https://svn.forgerock.org/opendj/trunk@2754 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2753 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2752 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
The user friendly names (UFN) are usually derived automatically from the component's "name" and "plural-name" attribute. However, sometimes these names are not that user friendly. For example, the names may be abbreviated forms (e.g. replication -> repl or password policy -> pwp). In these cases it would be nice to be abled to display the full human friendly name in help and documentation. This change includes an overridden UFN for the global configuration. So we should stop seeing messages in applications like "The Global was updated successfully". git-svn-id: https://svn.forgerock.org/opendj/trunk@2751 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
The total update was failing because the updated server was badly exiting the loop of meessage reception when it was receiving a message other than total update messages. This was caused by a mis-placed return null statement . git-svn-id: https://svn.forgerock.org/opendj/trunk@2750 41b1ffd8-f28e-4786-ab96-9950f0a78031
22 Aug, 2007
6 commits
-
…ration was incorrectly called "base-level" Fix for issue 2134 git-svn-id: https://svn.forgerock.org/opendj/trunk@2748 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
…rguments that allow the task to be scheduled to run in the directory server's JVM through the task interface as well as through the existing method or operating within the running JVM. - This introduces several classes that handle the plumbing of scheduling a task: LDAPConnectionArgumentParser: an argument parser that comes pre-populated with the common options used to specify an LDAP connection and includes a method for creating a connection TaskScheduleInformation: source of information important for creating the scheduled task entry in the backend TaskScheduleClient: interacts on behalf of clients that wish to schedule tasks TaskTool: base class that the tools can implement to handle decision about whether to operate locally or remotely - For export-ldif I removed the short identifier -w for the wrap options since it conflicted with the -w password option. - For import-ldif I removed the short identifiers -K for skipFile and -q for quiet since they conflicted with the options for specifying the keystore path and startTLS options respectively. git-svn-id: https://svn.forgerock.org/opendj/trunk@2743 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2742 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
When using the setup to configure 2 servers in multimaster mode. The setup first creates the configuration of the first server and start it When the second setup is run to configure the second server, the setup updates the configuration of the replication-server on the first server, however the code for handling this dynamic configuration was not yet written and this information is not taken into account. The replication servers are therefore not connected and the replication server on the new host therefore does not get the updates. These changes implement the dynamic configuration of replication servers so that the same scenario works fine. The only properties that is now not dynamically configurable is the path of the changelog database. A new test has been added for these changes. I've also tested manually that this does fix the replication server problem after configuration using the setup program. git-svn-id: https://svn.forgerock.org/opendj/trunk@2740 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
The replication monitoring information already provides the attribute unresolved-naming-conflicts that counts the number of conflicts that was not automatically resolved since last startup. The conflicting entries are also marked with the ds-sync-confict attribute so that administrators can look for these entries using filter ds-sync-confict=* This code add the generation of an administrative alert when a conflict is detected so that administrators can be made aware of the problem. git-svn-id: https://svn.forgerock.org/opendj/trunk@2737 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
Before this fix, If one remove the root entry of a replication domain, then stop the server The PersistentServerState is lost. Therefore when later restarting the server all the changes from the replication server are replayed on the database. To avoid this the fix is simply to store the PersistentServerState to the configuration entry when the root entry does not exist. I have not developed a unit test for this scenario because I believe that it is not possible to restart the server during the unit test. I have done manual tests to check that the PersistentServerState is correctly saved and reread. git-svn-id: https://svn.forgerock.org/opendj/trunk@2736 41b1ffd8-f28e-4786-ab96-9950f0a78031
21 Aug, 2007
5 commits
-
- sanitize backend handling in clearSubtree method. git-svn-id: https://svn.forgerock.org/opendj/trunk@2734 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
…only the INFO severity. Add some methods in the SecureConnectionCliParser that will be used by the replication CLI utilities. git-svn-id: https://svn.forgerock.org/opendj/trunk@2733 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2725 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2722 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
attribute uniqueness. The plugin has the following features: - provides ability to specify a group of attribute types that must have unique values; if no attribute types are specified then the plugin allows the operations to proceed with no checking - provides ability to specify a set of base DNs that limit the scope of the uniqueness checking; if no base DNs are specified the server's public naming contexts are used - allow changing of these configuration options without server restart - allows the uniqueness checking to span multiple base DNs; if the server's public naming contexts are used, then the specified attribute type values must be globally unique within the server Two configuration attributes have been added: 1. ds-cfg-unique-attribute-type used to specify the unique attribute type(s) 2. ds-cfg-unique-attribute-base-dn used specify the base DN(s) to limit the search scope A disabled plugin configuration has been added to the config.ldif file for the uid attribute: dn: cn=UID Unique Attribute ,cn=Plugins,cn=config objectClass: top objectClass: ds-cfg-plugin objectClass: ds-cfg-unique-attribute-plugin cn: UID Unique Attribute ds-cfg-plugin-class: org.opends.server.plugins.UniqueAttributePlugin ds-cfg-plugin-enabled: false ds-cfg-plugin-type: preOperationAdd ds-cfg-plugin-type: preOperationModify ds-cfg-plugin-type: preOperationModifyDN ds-cfg-unique-attribute-type: uid Issue 258. git-svn-id: https://svn.forgerock.org/opendj/trunk@2721 41b1ffd8-f28e-4786-ab96-9950f0a78031
20 Aug, 2007
6 commits
-
…eicfy the server root for DirectoryServer operations (issue 2121) git-svn-id: https://svn.forgerock.org/opendj/trunk@2711 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
in Java 6. git-svn-id: https://svn.forgerock.org/opendj/trunk@2709 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
allows third-party LDAP SDKs to be used to perform internal operations within the server. Rather than performing network communication, the custom socket decodes the request written to it, converts it to an internal operation, processes the request, and encodes the response so that it can be read from the socket by the LDAP SDK. This has been tested with both the Mozilla LDAP SDK for Java (which requires a trivial custom LDAPSocketFactory implementation) and JNDI (which requires a custom property to be set). git-svn-id: https://svn.forgerock.org/opendj/trunk@2706 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
- make toVerboseString method private in implementation classes. - make toVerboseString use StringBuilder instead of string concat. - make toVerboseString use ServerConstants.EOL where required. git-svn-id: https://svn.forgerock.org/opendj/trunk@2694 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2688 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
the consistency in the replication topology in the (hopefully) rare case when hardware failure or software bugs could break it (issue 788 and 791) There are several parts in this commit : - a new log file called replication was added. It's purpose is to store all the consistency errors detected by the replication with enough information to allow the administrator to repair the problem. This file is configured by default and contain only the replication errors, To achieve the a new log severity keyword "None" has been created so that the associated error log publisher does not print any error not related to replication. (I will update the reference guide after this commit) - a new control (the replication repair control) has been added. When this control is used in a MODIFY, DELETE, ADD or MODDN operation the operation is marked as a non-replicated replication operation. This cause the following : - The operation is allowed to modify attributes that are normally not allowed to be modified or added (NO-USER-MODIFCATION) such as entryuuid and ds-sync-hist To achieve this I add to move those checks from the AddOperationBasis.getObjectClasses() or AddOperationBasis.getUserAttributes() to the LocalBackendWorkflowElement.processAdd() but this has already been reviewed. - no change number is associated to the operation. - the operation is not published to the replication server and is therefore a local only operation. - the replication don't try to solve conflict or generate historical information for this operation. The intended usage of this control is that the administrator will check for errors in the replication log, determine the entries that have inconsistent values and use the control to repair them. I will write some documentation explaining in more details how to do this. - even though this is not related to replication repair I also took advantage of this change to add the multimaster replication synchronization provider in the default configuration. This will make configuration of replication using dsconfig easier because the user will now only need to configure the replication servers and replication domains. git-svn-id: https://svn.forgerock.org/opendj/trunk@2687 41b1ffd8-f28e-4786-ab96-9950f0a78031
19 Aug, 2007
2 commits
-
- fix bugs found by entry cache unit tests. - sanitize backend map maintenance. git-svn-id: https://svn.forgerock.org/opendj/trunk@2684 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
A new global property has been added to be able to specify to use a ClassLoader that limits the search of the bundles to the jar containint the Messages class i f we are running WebStart setup/upgrader. This property is only set in the quic ksetup.properties file, so the current behavior is preserved for all the other m essages files. The MessageDescriptor constructors have also been modified and n ow require a ClassLoader as parameter. With this modifications we have a ClassL oader defined in QuickSetupMessages.java that will only be used if we are runnin g QuickSetup. The JnlpProperties have been moved to SetupUtils so that the mess ages classes only depend on classes on the org.opends.server classes that can be compiled independently. git-svn-id: https://svn.forgerock.org/opendj/trunk@2682 41b1ffd8-f28e-4786-ab96-9950f0a78031
18 Aug, 2007
1 commit
-
The code was returning the raw version of the Message object that was being passed as parameter instead of the modified String. git-svn-id: https://svn.forgerock.org/opendj/trunk@2681 41b1ffd8-f28e-4786-ab96-9950f0a78031
17 Aug, 2007
12 commits
-
- Format string cannot end with '.' (QUICKSETUP and ADMIN_TOOLS excluded) - Categories cannot span multiple files and files cannot define messages in multiple categories Addional methods for MessageDescriptorRegistry to access descriptors by defining class Corrected some offending format strings Corrected message property file boilerplates and help comments git-svn-id: https://svn.forgerock.org/opendj/trunk@2677 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
…ect as an ADSContext.ServerProperty. Use the String representation instead. git-svn-id: https://svn.forgerock.org/opendj/trunk@2675 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
…turns Message objects. git-svn-id: https://svn.forgerock.org/opendj/trunk@2674 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2672 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
Fix a bug that made the label of the server location not to appear as invalid when we detected that the installation path was not valid. Fix a bug in UIFactory so that the invalid labels have again a red color. git-svn-id: https://svn.forgerock.org/opendj/trunk@2671 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
… quicksetup.jar (OpenDsException) and fix some code to also add the messages properties files. Only QuickSetupMessages are required, so these are the only messages that are being added. git-svn-id: https://svn.forgerock.org/opendj/trunk@2670 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
… This biggest issues here is the reversion of the Validator class to use String based messages instead of the message framework as the class is only used internally. git-svn-id: https://svn.forgerock.org/opendj/trunk@2669 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
… ADS and of guitools). git-svn-id: https://svn.forgerock.org/opendj/trunk@2668 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
The DatabasesTableModel now returns for several values Message objects. Update the DatabaseTableCellRenderer to take this into account. git-svn-id: https://svn.forgerock.org/opendj/trunk@2667 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
… listener state as it does for the other columns. git-svn-id: https://svn.forgerock.org/opendj/trunk@2666 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
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. git-svn-id: https://svn.forgerock.org/opendj/trunk@2665 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
initialize the proper internal structures so that OpenDS code can be more easily used for client-side applications that could benefit from the code but don't want or need to be running in the same JVM as the server. Also, update the DirectoryServer.bootstrapClient() method (which is what EmbeddedUtils.initializeForClientUse() uses behind the scenes) can be called multiple times on the same server instance without interfering with any previous initialization that might have been done. In short, it will ensure that this initialization occurs no more than once during the life of the DirectoryServer object instance. git-svn-id: https://svn.forgerock.org/opendj/trunk@2664 41b1ffd8-f28e-4786-ab96-9950f0a78031
16 Aug, 2007
1 commit
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2662 41b1ffd8-f28e-4786-ab96-9950f0a78031