directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pierre-Arnaud Marcelot (JIRA)" <>
Subject [jira] Updated: (DIRSERVER-679) Tools improvement and add of Export Command and JUnit tests
Date Fri, 21 Jul 2006 13:25:16 GMT
     [ ]

Pierre-Arnaud Marcelot updated DIRSERVER-679:

    Attachment: patch.txt

Here's the patch

> Tools improvement and add of Export Command and JUnit tests
> -----------------------------------------------------------
>                 Key: DIRSERVER-679
>                 URL:
>             Project: Directory ApacheDS
>          Issue Type: Improvement
>          Components: tools
>    Affects Versions: 1.0-RC3
>            Reporter: Pierre-Arnaud Marcelot
>            Priority: Minor
>         Attachments: patch.txt
> Working on a new plugin supporting LDIF Import/Export for LDAP Studio (
), I wanted to use the Apache DS to import an LDIF file.
> But the Import Command can only be accessed via a Command Line and don't give enough
feedback for a front-end GUI (particularly to show the progress of the operation).
> Emmanuel (L├ęcharny) also pointed out the fact that it may be interesting for future
developments to be able to access the Tools in a "kind of" Client/Server way. The tools running
on a the server's station, and the command launched from another machine.
> So, he asked me to modify the tools to add this Client/Server feature and make them callable
more easily from other application and give better feedback.
> I made a small documentation on this on Safehaus :
. It is also attached to this post as a PDF, since LDAPStudio's Confluence isn't accessible
to everyone.
> In the patch you'll find the tools with the new architecture (defined with Emmanuel).
> I also added a new command that export entries as LDIF file, and some JUnit tests for
the Import, Export and GracefulShutdown command.
> Feel free to give me your feedback about this.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message