09 Jun, 2007
1 commit
-
- [Issue 1767] Checksum error message on startup - Set eol-style to native git-svn-id: https://svn.forgerock.org/opendj/trunk@2064 41b1ffd8-f28e-4786-ab96-9950f0a78031
08 Jun, 2007
11 commits
-
…ways exported before top entry. Clone the database config so that we don't share it between different databases. git-svn-id: https://svn.forgerock.org/opendj/trunk@2063 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
determining the length of time the account will remain locked due to authentication failures (it was supposed to be reported in seconds, but the value returned was in milliseconds). This only impacted components that reported the time until the account was unlocked and not any calculation determining whether an account should currently be locked. OpenDS Issue Number: 1781 git-svn-id: https://svn.forgerock.org/opendj/trunk@2062 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
- After discussing the previously noninteractive option with Brian, I changed the CLI options somewhat. The new CLI design is to specify an interactive option (if interactivity is desired) rather than to have to specify non-interactivity. Additionally interactivity is only supposed to apply to gathering of required information and not whether or not and application is allowed to prompt for such things as continuation following an error. To suppress these sort of prompts you should specify the silent option. So the common plumbing (currently not used by setup or uninstall) now operates as described above and the upgrader now has a both silent and interactive options as described. - Make BuildExtractor a Launcher. BuildExtractor is a simple program used by the CLI for unzipping an OpenDS .zip file. Previously is was not very smart, relying on the Upgrader to report status and make sure the unzipping went OK. This had the unfortunate side-effect of making the scripts overly complicated resulting in issue 1772, and made it difficult to support interactivity. So the BuildExtractor has been made smarter so that it is capable of parsing the complete command line invocation, printing usage, and performing verification that it performed properly. - Addresses issue 1772 by simplifying and correcting the upgrade and upgrade.bat scripts. git-svn-id: https://svn.forgerock.org/opendj/trunk@2061 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2060 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
…the performance of the loggers when they are disabled. Fixed for issue 1780 git-svn-id: https://svn.forgerock.org/opendj/trunk@2059 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
…ibutes * and operational attributes +. Issue 1745. git-svn-id: https://svn.forgerock.org/opendj/trunk@2058 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
This decision was taken in an admin meeting and the main reasons are that there are lots of users that may dislike the idea of OpenDS modifying the Windows Service Registry as they are not using it in production (yet). Moreover there is a bug (1603) that prevents registering the server as a service on Vista, so these modifications will allow to the users to use the graphical setup on that OS. git-svn-id: https://svn.forgerock.org/opendj/trunk@2057 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
When we install OpenDS on windows with no Windows Service configured (this is the case where this issue was reproduced) and we launch start-ds.bat the BufferedOutputReaders are kept open. The fix consists of waiting at most a certain time once the server sent the msg ID informing that it was successfully started. git-svn-id: https://svn.forgerock.org/opendj/trunk@2056 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
…st whether we use the winlauncher.exe or not for the setup and the uninstall. git-svn-id: https://svn.forgerock.org/opendj/trunk@2055 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
…tion using the setup. Some tests have been done to check that the code is working but there are some additional things to verify before making the new functionalities visible. That is why the new functionalities have not been made available in the setup interface. In order to be able to see the new functionalities some commented lines must be uncommented in Uninstaller.java (search for some 'TODO' comments in the code). git-svn-id: https://svn.forgerock.org/opendj/trunk@2054 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
The fixes included the handling of quite a lot of errors that might be generated by the Administration Framework. The creation of the Administrators has been revisited and now they use the privilege system and no acis are defined (which implies that no modification to the configuration is required in order the administrators to work). git-svn-id: https://svn.forgerock.org/opendj/trunk@2053 41b1ffd8-f28e-4786-ab96-9950f0a78031
07 Jun, 2007
7 commits
-
…yCache() method that takes the default cache initialization out of initializeEntryCache() method. the default entry cache will be initialized before backends initialization thus resolving issues like NPE via AciListenerManager etc. git-svn-id: https://svn.forgerock.org/opendj/trunk@2052 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
use a privilege of "unindexed-search" instead. Also, eliminate the index-rebuild privilege and fold all of its functionality into ldif-import, since having a separate privilege for it doesn't provide much benefit and creates additional administrative overhead. OpenDS Issue Numbers: 1765, 1776 git-svn-id: https://svn.forgerock.org/opendj/trunk@2051 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
for entries in private backends (e.g., the root DSE, schema, monitor entries, config entries, etc.). The entryUUID value that will be generated is based on an MD5 hash of the entry DN, but this shouldn't be a problem for entries in private backends because none of them allow modify DN operations. User entries should have a real entryUUID value generated when the entry is created (either via an LDAP add or an LDIF import). OpenDS Isssue Number: 1775 git-svn-id: https://svn.forgerock.org/opendj/trunk@2050 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
element that includes flags that indicate how the entry was encoded. The flags currently defined include: - Whether to exclude the DN from the encoded entry. This may be useful for the filesystem entry cache, since it will already have a reference to the DN. - Whether to compress the set of object classes contained in the entry with a binary token. - Whether to compress the attribute descriptions in the entry with binary tokens. These changes can help improve the encode/decode performance, and can reduce the entry footprint (by about 30% for entries based on the example.template). None of these options are enabled at the present time, but components which call the Entry.encode() method will be able to indicate which of them should be used for that entry. OpenDS Issue Numbers: 660, 1675, 1770 git-svn-id: https://svn.forgerock.org/opendj/trunk@2049 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2048 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
- Brings the quicksetup code to "internationalized with possible i18n bugs" to address issue 1629. In other words I moved messages formerly coded as string literals (with the exception of log messages and non-ApplicationException exception messages) presented to the user into resource bundles. - Fixes small miscellaneous issues that Idea complains about (e.g. unnecessary casts, variable initialization). - Moves some commonly defined string literal and constants to a single Constants file. - Trimmed a little dead code. git-svn-id: https://svn.forgerock.org/opendj/trunk@2047 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
Considering the limited added value that the JMX port will provide on 1.0 and the fact that we do not want to expose it on the QuickSetup, in the admin group we consider to disable this port by default. Before committing a fix for this maybe we should send a Heads Up message to the users mailing list. Basically after the changes the JMX connection handler will not be enabled if the server is installed using the graphical setup. For the command line setup, JMX will not be enabled unless the user explicitly includes de -x option (for the JMX port) when invoking the command-line. git-svn-id: https://svn.forgerock.org/opendj/trunk@2046 41b1ffd8-f28e-4786-ab96-9950f0a78031
06 Jun, 2007
9 commits
-
directory. In particular, this commit exposes the LDAPClientConnection.sendLDAPMessage() method, and fixes a case in which short-circuiting out of the add operation processing in the pre-parse code with a success response could have resulted in a null pointer exception. OpenDS Issue Number: 1729 git-svn-id: https://svn.forgerock.org/opendj/trunk@2045 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
ldapCompareWithScript, and ldapPasswordModifyWithScript. git-svn-id: https://svn.forgerock.org/opendj/trunk@2044 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2043 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
…end initialization. Issue #1750. git-svn-id: https://svn.forgerock.org/opendj/trunk@2042 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
…ne with a localized message since this the message contained in this exception is exposed to end users. - A few instances of ApplicationException in Application.create() were converted to throw RuntimeException since the formerly thrown ApplicationExceptions were caught and converted to RuntimeExceptions anyway. End users will never see these exceptions unless there is something seriously wrong. - All other instances of hard-coded messages were put in the messages properties file. git-svn-id: https://svn.forgerock.org/opendj/trunk@2041 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2040 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
Put the references to colors in the properties files. This has been done because the meaning of the colors vari es in the countries so the use of one color or the other can be related to the language. git-svn-id: https://svn.forgerock.org/opendj/trunk@2039 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2038 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2037 41b1ffd8-f28e-4786-ab96-9950f0a78031
05 Jun, 2007
12 commits
-
they pass the server unit tests. git-svn-id: https://svn.forgerock.org/opendj/trunk@2036 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2035 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2034 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
…the upgrader's interaction in asking the user whether they would like to cancel an upgrade if there are problems found: - The notion of a 'UserInteraction' which can be used by applications to prompt the user regardless of whether or not they are running in CLI or GUI mode. There are two subclasses of this, one for the CLI and one for the GUI. Unlike existing code for prompting the user in the CLI UserInteraction is intended to be used during the coarse of the progress panel but can be used elsewhere as well. UserInteraction has two methods currently that take arguments similar to JOptionPane's showConfirmDialog. One of the methods allows an application to present the user a dialog having a 'Details' section which in the GUI shows the user a JOptionPane have a 'Show Details' button that when clicked expands the panel to show details. Care has been taken to extend JOptionPane rather than invent a new dialog whose look and feel may not be compatible with future Swing look and feels. - Code for the upgrader to use the new functionality in asking the user if they would like to back out of an upgrade if there are errors found. The user is presented with an option pane in the GUI with a 'Show Details' button where they can get more information. The CLI has an option for viewing the details if in an interactive session. The previous behavior was to back out automatically. The upgrader CLI supports a noninteractive argument to support the current behavior. - Common support for 'silent' and 'noninteractive' command line parsing. The uninstaller and installer still retain their separate method for determining this but they could easily adopt the common approach now present in CliApplicationHelper. git-svn-id: https://svn.forgerock.org/opendj/trunk@2033 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2032 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
- remove FSCache. git-svn-id: https://svn.forgerock.org/opendj/trunk@2031 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2030 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2029 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2028 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2027 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@2026 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
If there is no replication server the domain will start anyway and will retry to connect regularly. The changes happening during this time will be sent to the replication server when it starts (currently only for modify operations) git-svn-id: https://svn.forgerock.org/opendj/trunk@2025 41b1ffd8-f28e-4786-ab96-9950f0a78031