org.forgerock / org.forgerock.opendj

23 Feb, 2007

15 commits

22 Feb, 2007

10 commits

  • c4009404   Update the access control config manager to send an administrative alert ... Browse Code » 
    notification whenever the access control handler is enabled or disabled.

OpenDS Issue Number:  1269


git-svn-id: https://svn.forgerock.org/opendj/trunk@1229 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson
     
  • 51a676be   Update the server configuration so that the access control handler points to ... Browse Code » 
    the dseecompat implementation by default.  It will still remain disabled by
default.

OpenDS Issue Number:  1270


git-svn-id: https://svn.forgerock.org/opendj/trunk@1228 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson
     
  • 06d7d1f5   This fixes a bug when the user provides only one parameter (-R or --restart). ... Browse Code » 
    
git-svn-id: https://svn.forgerock.org/opendj/trunk@1227 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     
  • f7068255   If the user provides no arguments or only the -R argument, we will assume that ... Browse Code » 
    we want to stop the local server an we use the pid to kill it.  If other
arguments are passed (which appart from --help are arguments related to LDAP
authentication) I will assume that we are trying to stop the server using
protocol.

This fixes issue 1261.


git-svn-id: https://svn.forgerock.org/opendj/trunk@1225 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     
  • 064d9cbb   Update the start-ds.bat batch file to use the --checkStartability option to ... Browse Code » 
    properly handle the case where the server is already running.

OpenDS Issue Number:  1251


git-svn-id: https://svn.forgerock.org/opendj/trunk@1221 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson
     
  • d4d0fcf8   Update the start-ds script and associated Directory Server code to ensure that ... Browse Code » 
    the PID file is only written if the server is not already running.  If it's not
being used to try to start the server, then just invoke the command without a
PID file.  If it is trying to start the server but the server is already
running, then exit with an error.

OpenDS Issue Number:  1251


git-svn-id: https://svn.forgerock.org/opendj/trunk@1220 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson
     
  • 45d83e74   Update the winlauncher source files to set svn:eol-style to "native". ... Browse Code » 
    
git-svn-id: https://svn.forgerock.org/opendj/trunk@1219 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson
     
  • 425747b6   Fix for Issues #1025 and #1248 ('stop-ds.bat should be able to stop server even … ... Browse Code » 
    …if LDAP port' and 'cannot stop server through status panel').

The goal of these changes is to be able to have exactly the same user interface in Windows and Unix to stop the server.  In windows we force the user to provide LDAP credentials even if the command is going to be run locally.  The goal is to allow to stop the server using only system credentials (as we do in UNIX) when the user does not provide arguments when calling stop-ds.bat.

In order to do this I have written some native code.  This native code is called when we start the server to:
1. Launch the java process and get the associated PID.
2. Create a server.pid file as we do for UNIX systems to store the PID of the process.

The native code that stops the server reads the PID file contents and tries to stop the process associated with the PID.

In order to allow the users to be able to build the product with independence of the platform, the binaries will be included with the source code.  The code used to generate these binaries will also be provided.

I have generated 1 executable called winlauncher.exe.  The binaries will be committed in the source tree under lib (with activation.jar and mail.jar).  They will also be installed under <server root>\lib.

The native code is in the files winlauncher.c and winlauncher.h.  These files are placed under the new directory build-tools/src/windows.

I have tried to keep the native code simple and leave as much logic as I could into the batch files (for instance everything related to the discovery of the java binaries) so that the administrators can play with them.

A README file has been also been included to explain how to generate the binaries.

Extras:
When we call start-ds from the command line, the server will not stop when the command prompt window is closed (unless start-ds was called to run in not-detached mode).  The next step is to register DS as a service to avoid the server to be stopped when the user logs out.

When we call setup (with no arguments) or the statuspanel the generated process (and windows) will no longer get killed when the command prompt window is killed.

When the user double-clicks on the setup.bat or the statuspanel.bat files, the command prompt window only appears briefly.  Today when we do this a command prompt window stays open until we close setup or the status panel window.


git-svn-id: https://svn.forgerock.org/opendj/trunk@1218 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     
  • d995f5be   Fix for Issues #1025 and #1248 ('stop-ds.bat should be able to stop server even … ... Browse Code » 
    …if LDAP port' and 'cannot stop server through status panel').

The goal of these changes is to be able to have exactly the same user interface in Windows and Unix to stop the server.  In windows we force the user to provide LDAP credentials even if the command is going to be run locally.  The goal is to allow to stop the server using only system credentials (as we do in UNIX) when the user does not provide arguments when calling stop-ds.bat.

In order to do this I have written some native code.  This native code is called when we start the server to:
1. Launch the java process and get the associated PID.
2. Create a server.pid file as we do for UNIX systems to store the PID of the process.

The native code that stops the server reads the PID file contents and tries to stop the process associated with the PID.

In order to allow the users to be able to build the product with independence of the platform, the binaries will be included with the source code.  The code used to generate these binaries will also be provided.

I have generated 1 executable called winlauncher.exe.  The binaries will be committed in the source tree under lib (with activation.jar and mail.jar).  They will also be installed under <server root>\lib.

The native code is in the files winlauncher.c and winlauncher.h.  These files are placed under the new directory build-tools/src/windows.

I have tried to keep the native code simple and leave as much logic as I could into the batch files (for instance everything related to the discovery of the java binaries) so that the administrators can play with them.

A README file has been also been included to explain how to generate the binaries.

Extras:
When we call start-ds from the command line, the server will not stop when the command prompt window is closed (unless start-ds was called to run in not-detached mode).  The next step is to register DS as a service to avoid the server to be stopped when the user logs out.

When we call setup (with no arguments) or the statuspanel the generated process (and windows) will no longer get killed when the command prompt window is killed.

When the user double-clicks on the setup.bat or the statuspanel.bat files, the command prompt window only appears briefly.  Today when we do this a command prompt window stays open until we close setup or the status panel window.


git-svn-id: https://svn.forgerock.org/opendj/trunk@1217 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     
  • b2f50ba6   Fix for Issues #1025 and #1248 ('stop-ds.bat should be able to stop server even … ... Browse Code » 
    …if LDAP port' and 'cannot stop server through status panel').

The goal of these changes is to be able to have exactly the same user interface in Windows and Unix to stop the server.  In windows we force the user to provide LDAP credentials even if the command is going to be run locally.  The goal is to allow to stop the server using only system credentials (as we do in UNIX) when the user does not provide arguments when calling stop-ds.bat.

In order to do this I have written some native code.  This native code is called when we start the server to:
1. Launch the java process and get the associated PID.
2. Create a server.pid file as we do for UNIX systems to store the PID of the process.

The native code that stops the server reads the PID file contents and tries to stop the process associated with the PID.

In order to allow the users to be able to build the product with independence of the platform, the binaries will be included with the source code.  The code used to generate these binaries will also be provided.

I have generated 1 executable called winlauncher.exe.  The binaries will be committed in the source tree under lib (with activation.jar and mail.jar).  They will also be installed under <server root>\lib.

The native code is in the files winlauncher.c and winlauncher.h.  These files are placed under the new directory build-tools/src/windows.

I have tried to keep the native code simple and leave as much logic as I could into the batch files (for instance everything related to the discovery of the java binaries) so that the administrators can play with them.

A README file has been also been included to explain how to generate the binaries.

Extras:
When we call start-ds from the command line, the server will not stop when the command prompt window is closed (unless start-ds was called to run in not-detached mode).  The next step is to register DS as a service to avoid the server to be stopped when the user logs out.

When we call setup (with no arguments) or the statuspanel the generated process (and windows) will no longer get killed when the command prompt window is killed.

When the user double-clicks on the setup.bat or the statuspanel.bat files, the command prompt window only appears briefly.  Today when we do this a command prompt window stays open until we close setup or the status panel window.


git-svn-id: https://svn.forgerock.org/opendj/trunk@1216 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     

21 Feb, 2007

7 commits

20 Feb, 2007

3 commits

19 Feb, 2007

2 commits

  • eff37a32   fix for issue 1212 namingConflict test trigger an assert from the static group ... Browse Code » 
    When it is enabled, the synchronization code can sometimes decide to abandon
an add operation. In such case the handleConflictResolution() method
of the SynchronizationProvider will return a code indicating to stop the
OperationProcessing.
However when doing this, the ChangeListener are still invoked
at the end of the AddOperation processing.
Since the operation has not been processed, the ChangeListeners are given
a null entry parameter but the StaticGroup code that runs as a ChangeListener
makes the assumptions that the entry is always non null at this point.
This currently causes the following assert when running the test
synchronization.UpdateOperationTest.namingConflicts()

The change notification listeners will only be invoked if the result
code for the operation is "SUCCESS", and at that point in the processing
it should only be SUCCESS if the update was actually applied.  If the
synchronization code decided to abort the operation the
the provider.handleConflictResolution() therefore now set
a Cancel Result code.







git-svn-id: https://svn.forgerock.org/opendj/trunk@1201 41b1ffd8-f28e-4786-ab96-9950f0a78031
    gbellato
     
  • c3dbba36   Resolve issue 1242 configDS should allow params for root DN and password ... Browse Code » 
    
git-svn-id: https://svn.forgerock.org/opendj/trunk@1200 41b1ffd8-f28e-4786-ab96-9950f0a78031
    gary_williams
     

18 Feb, 2007

3 commits