| bf6595bd41588352488523b25d859a700e5013bf 4081 |
|
02-Apr-2008 |
lutoff |
Fix for issue #3041 (ldapsearch: trailing arguments are not interpreted as attributes when --filename option is specify)
Trailing arguments should be structured as follow:
- If a filter file is present, trailing arguments are considered
as attributes
- If filter file is not present, the first trailing argument is
considered the filter, the other as attributes. |
| cddd676de138668ef547099bba407d8b302a1507 3210 |
|
26-Sep-2007 |
kenneth_suter |
Addresses issue 2143 which is intended to help with the readability of the usage statements by allowing options to be grouped logically by type. Many of the utilities arguments have grown to such an extent that it is difficult to sort through the various types of arguments to find what you are looking for. For instance the usage statement for the task schedulable arguments are mixed with the LDAP connection arguments which makes them difficult to ignore if they want to use the tool in offline mode.
This code also make consistent the position of standard options (e.g. help, version, quiet, verbose) within usage statements.
ArgumentParser (and SubCommandArgumentParse) have 4 built-in groups: General Options (for help and version commands), LDAP Connection Options (e.g. host, port), Utility Input/Output Options (e.g. quiet, verbose, no-prompt, argument file etc) and default options (for ungrouped arguments). The default group appears first in the list without a header to maintain backward consistency. Other groups can be defined for a usage statement by supplying an ArgumentGroup to the addArgument() method. |
| 0b8437a722e1ddb79927fecd6242f21a6c383c1c 1786 |
|
03-May-2007 |
david_page |
Issue [1395] NullPointerException raised by ldapsearch when prompt for bind passwd
When "-w -" is passed to a command-line tool such as ldapsearch, the tool requests the bind password from standard input. OpenDS on Java 6 uses java.io.Console.readPassword method. For prior releases a utility method org.opends.server.util.PasswordReader.readPasswordUsingBackspaces is used, and this routine returns a char[] with the user-supplied password, which is used to initialize a String. In the case no password was supplied (i.e., the user just presses return at the prompt), the routine returns null, which results in an exception. This change returns char[0] in the case of an empty password, which mimics the behavior of the Java 6 java.io.Console.readPassword, and eliminates the exception. |
| a802a67804045dbf22a056761b54493321f15202 727 |
|
15-Nov-2006 |
neil_a_wilson |
Update the LDAPSearch, LDAPModify, LDAPCompare, and LDAPDelete tools to rename
the "--controls" argument to "--control", since each instance only allows the
user to specify information about a single control. Issue #1009.
Update the LDAPSearch, LDAPModify, LDAPCompare, and LDAPDelete tools to allow
multiple instances of the "-J"/"--control" argument to specify multiple
arbitrary controls. Issue #1010. |
| 266c5071a91fda6a5159b08ea8d45261228d03d5 702 |
|
11-Nov-2006 |
neil_a_wilson |
Make a number of changes to administrative tools provided with OpenDS. These
are all made under the umbrella of issue #994, but there are individual issues
for each change.
- Issue #979 -- Re-order LDAP tool arguments
When displaying usage information for many of the LDAP tools (e.g.,
ldapsearch, ldapmodify, etc.), the arguments were not provided in any kind of
logical grouping. This has been corrected so that the arguments are listed
in a more logical ordering.
- Issue #983 -- Add tool description to argument parser
When displaying usage information for administrative tools, it now includes a
small summary of what the tool does at the top of the argument list.
- Issue #984 -- Make tool usage more compact
Previously, the tool usage included a blank line between each argument, which
made the usage information seem too verbose, especially for tools like
ldapsearch with a lot of arguments. This extra space has been removed.
Also, many of the argument descriptions have been rewritten in an attempt to
avoid requiring multiple lines.
- Issue #985 -- Wrap long output in administrative tools when appropriate
Update most of the output for the administrative tools so that it is easier
to read on 80-column displays. This primarily impacts error message, and
cases in which the format of the output is important (e.g., LDIF output from
ldapsearch) no changes were made.
- Issue #986 -- Eliminate hard-coded strings in tools
Some of the tools had hard-coded strings used for error and warning messages.
They have been replaced with localizeable output from the messages files.
- Issue #990 -- LDAP tools don't use trust store password
The LDAP tools didn't provide any mechanism for specifying the PIN needed to
access the contents of an SSL trust store. Some types of trust stores may
require a PIN to access them, so it is now possible to either directly
specify the PIN or to provide the path to a PIN file.
- Issue #991 -- Disconnect when running stop-ds shouldn't be an error
When using the stop-ds script, if the server began shutting down before it
returned a response to the client, the client would provide an error message
making it sound like something went wrong. The output has now been updated
to indicate that the server is likely in the course of shutting down.
- Issue #992 -- Tool usage should include the tool name rather than the class
When displaying usage information for the administrative tools, the
fully-qualified class name for the Java class was displayed, where the name
of the shell script or batch file would have been more useful. |