02 Mar, 2007
13 commits
-
type and the ds-cfg-dseecompat-access-control-handler object class. git-svn-id: https://svn.forgerock.org/opendj/trunk@1310 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
programmatically from within the same JVM as the server. This will make it much easier to call them from unit tests. OpenDS Issue Number: 1311 git-svn-id: https://svn.forgerock.org/opendj/trunk@1309 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@1308 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
This was caused by a null pointer exception that we previously got away with but became noticable since the ACI cache update is now atomic. git-svn-id: https://svn.forgerock.org/opendj/trunk@1306 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@1305 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
…ion and using configure script. In the QuickSetup I added some code to *temporarily* select a port that is not being used for JMX. Today we do not inform the user of the existence of this port so this approach does not make things much worse and reduces the changes of port conflicts in general. Even in the case where we are not installing multiple instances of OpenDS the port 1689 might be in use by another process. git-svn-id: https://svn.forgerock.org/opendj/trunk@1303 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@1302 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@1301 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@1300 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@1298 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
The synchronization protocol already have some re-synchronization capabilities that allows the synchronization server to detect where to start from the changelog when a new LDAP server opens a session. These changes implements the ability to do this when a restore or an import is done when the LDAP server is online and already connected to a synchronization server. To achieve this the synchronization code, on notification from the core server that a restore or an import is starting, close the session to the synchronization server and restart it when the restore or import is finished. The synchronization protocol then does its job of negociating where to start from the changelog and resynchronizing the LDAP Server. The core server does not yet provide the notification to the changelog server but here if the synchronization part of the code along with some test for it. git-svn-id: https://svn.forgerock.org/opendj/trunk@1296 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
"server-cert" rather than "adm-server-cert". git-svn-id: https://svn.forgerock.org/opendj/trunk@1295 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
…le issue on installer files. added javadoc target to generate functional tests documentation. added email capability in the run-daily target. config.py.stubs is back to referencing python variables. git-svn-id: https://svn.forgerock.org/opendj/trunk@1294 41b1ffd8-f28e-4786-ab96-9950f0a78031
01 Mar, 2007
12 commits
-
…ger.debugCought should be debugCaught). git-svn-id: https://svn.forgerock.org/opendj/trunk@1293 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
…g when reading the ACI cache. Remove the linked list field from the Aci class and use the standard LinkedList instead. git-svn-id: https://svn.forgerock.org/opendj/trunk@1292 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
… from the new debug logging framework. Also removed some redundent exception printing calls in favor or just one debugCought. Replaced System.out.println calls in RootContainer and JebFormat to debugInfo calls. Fix for issue 854 git-svn-id: https://svn.forgerock.org/opendj/trunk@1291 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@1290 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@1287 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
debugEnter and debugConstructor calls. git-svn-id: https://svn.forgerock.org/opendj/trunk@1286 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@1285 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@1284 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@1283 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
This removes old debug logging framework method calls that are going to be automatically instrumented by AspectJ. Non instrumented debug method calls are updated to use the new debug framework methods. However, the new debug logging framework is not yet active as the Aspects are not weaved in. After this revision, debug logging will be disabled in the server until the new AOP framework is complete. - Removed debugEnter and debugConstructor from all source files. - Removed CLASS_NAME static string for debug purposes. - Removed old debug logging framework. - Added new debug logging frameworking using AOP. - Added AspectJ binary and libraries. - Change all modified files copyrights to include 2007. git-svn-id: https://svn.forgerock.org/opendj/trunk@1282 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@1281 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
…atically instrumented by AspectJ. Non instrumented debug method calls are updated to use the new debug framework methods. However, the new debug logging framework is not yet active as the Aspects are not weaved in. After this revision, debug logging will be disabled in the server until the new AOP framework is complete. - Removed debugEnter and debugConstructor from all source files. - Removed CLASS_NAME static string for debug purposes. - Removed old debug logging framework. - Added new debug logging frameworking using AOP. - Added AspectJ binary and libraries. - Change all modified files copyrights to include 2007. git-svn-id: https://svn.forgerock.org/opendj/trunk@1280 41b1ffd8-f28e-4786-ab96-9950f0a78031
28 Feb, 2007
10 commits
-
should be presented based on its alias (aka its nickname). This is used both by server-side code which needs to present a certificate to clients, as well as by client-side code which needs to present a certificate to the server. OpenDS Issue Number: 1292 git-svn-id: https://svn.forgerock.org/opendj/trunk@1279 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@1278 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
PasswordPolicy.requireSecureAuthentication (via PasswordPolicyState.getPolicy). I had missed this call in an earlier commit. git-svn-id: https://svn.forgerock.org/opendj/trunk@1277 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
PasswordPolicy.requireSecureAuthentication (via PasswordPolicyState.getPolicy). I had missed this call in an earlier commit. git-svn-id: https://svn.forgerock.org/opendj/trunk@1276 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
configuring synchronization for suffix cn=schema (issue 613) . You may want to read the schema Synchronization documents before reviewing this https://opends.dev.java.net/public/docs/dev-docs/SchemaSyncFeatureRequirements.html and https://opends.dev.java.net/public/docs/dev-docs/SchemaSyncDesign.html It includes : - Change the PersistentServerState to use attribute ds-sync-state in the base entry instead of a specific entry. Add new unit test for the PersistentServerState class. Change attribute ds-sync-state to be an operational attribute. - Change the schema backend to allow storage of the ds-synch-state attribute in the schema ldif File. This change is arguable because I have chosen to make this as simple as possible and therefore only allowed the storage of this attribute in the schema File. While this has the advantage of being very simple it has the drawback of adding some code in the schema backend that is only related to synchronization. The other choice would be to add a generic service in the schema backend for storing any type of attribute. Please tell me if you think that this would be better. - Disable the conflict resolution for cn=schema so that we don't polute the ldif entries with the historical information - Add unit test for schema synchronization The work for schema synchronization is not complete with this. A second round of modification is necessary for synchronizing the schema changes done by manually editing the files or by dynamically loading a file. git-svn-id: https://svn.forgerock.org/opendj/trunk@1275 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
This change makes possible to configure the Changelog purge delay that was previously hard-coded using the ds-cfg-changelog-purge-delay attribute. git-svn-id: https://svn.forgerock.org/opendj/trunk@1274 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@1273 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
The problem was caused because in the class InstallDS the check for the port was not performed when the user already provided the port through the command line (see first diffs in InstallDS). The rest of the diffs consist of factorization of code to be shared between the quicksetup classes and the class org.opends.server.tools.InstallDS. Some methods from the Utils class of quicksetup have been moved to the SetupUtils class; these methods allow to know if a given port is priviledged or not, if we can use it to configure the server and to know in which Operating System the JVM is running. The operating system methods use the enumeration OperatingSystem (which has been slightly modified to not have dependencies on other classes and to be included in quicksetup.jar). Extra: use the class LockFileManager to know if the server is running or not. The use of this class does not impact the Web Start Installer as we only want to know if the server is running or not once we have tried to start it (and so OpenDS.jar has already been loaded by the class loader). git-svn-id: https://svn.forgerock.org/opendj/trunk@1272 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
draft-wahl-ldap-session and the new draft-zeilenga-sasl-yap document. git-svn-id: https://svn.forgerock.org/opendj/trunk@1270 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
. run the functional tests on windows . download the daily build and install it to run the functional tests . gather test coverage by editing the package on the fly to launch emma git-svn-id: https://svn.forgerock.org/opendj/trunk@1269 41b1ffd8-f28e-4786-ab96-9950f0a78031
27 Feb, 2007
4 commits
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@1267 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
git-svn-id: https://svn.forgerock.org/opendj/trunk@1265 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
Neil for issue #1266: use a hidden option to check whether the server is already running or not. If the server is not running the message 'Server already stopped' is displayed, if the server is running the message 'Stopping Server... is displayed'. So the output of the command with this changes is: If the server is running ======================== bash-3.00$ bin/stop-ds --restart Stopping Server... [23/Feb/2007:17:00:28 +0100] category=CORE severity=NOTICE id=458886 msg="OpenDS Directory Server 0.1.0 starting up." [23/Feb/2007:17:00:34 +0100] category=BACKEND severity=NOTICE id=8847402 msg="A database backend containing 1 entries has started." [23/Feb/2007:17:00:34 +0100] category=CONFIG severity=SEVERE_WARNING id=3277325 msg="Access control has been disabled." [23/Feb/2007:17:00:35 +0100] category=CORE severity=NOTICE id=458887 msg="The Directory Server has started successfully." [23/Feb/2007:17:00:35 +0100] category=CORE severity=NOTICE id=458891 msg="The Directory Server has sent an alert notification generated by class org.opends.server.core.DirectoryServer (alert type org.opends.server.DirectoryServerStarted, alert ID 458887): The Directory Server has started successfully.." bash-3.00$ bash-3.00$ bin/stop-ds If the server is stopped ======================== bash-3.00$ bin/stop-ds Server already stopped. bash-3.00$ bin/stop-ds --restart Server already stopped. [23/Feb/2007:16:59:50 +0100] category=CORE severity=NOTICE id=458886 msg="OpenDS Directory Server 0.1.0 starting up." [23/Feb/2007:16:59:55 +0100] category=BACKEND severity=NOTICE id=8847402 msg="A database backend containing 1 entries has started." [23/Feb/2007:16:59:56 +0100] category=CONFIG severity=SEVERE_WARNING id=3277325 msg="Access control has been disabled." [23/Feb/2007:16:59:57 +0100] category=CORE severity=NOTICE id=458887 msg="The Directory Server has started successfully." [23/Feb/2007:16:59:57 +0100] category=CORE severity=NOTICE id=458891 msg="The Directory Server has sent an alert notification generated by class org.opends.server.core.DirectoryServer (alert type org.opends.server.DirectoryServerStarted, alert ID 458887): The Directory Server has started successfully.." git-svn-id: https://svn.forgerock.org/opendj/trunk@1263 41b1ffd8-f28e-4786-ab96-9950f0a78031
-
the new certificate mappers, as well as the ds-cfg-changelog-purge-delay attribute. git-svn-id: https://svn.forgerock.org/opendj/trunk@1262 41b1ffd8-f28e-4786-ab96-9950f0a78031
26 Feb, 2007
1 commit
-
The start TLS test suite no longer allows the rest of the tests to run without failing. git-svn-id: https://svn.forgerock.org/opendj/trunk@1261 41b1ffd8-f28e-4786-ab96-9950f0a78031