[ 
https://issues.apache.org/jira/browse/DIRSERVER-922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12521138
 ] 

Pierre-Arnaud Marcelot commented on DIRSERVER-922:
--------------------------------------------------

As Emmanuel explained, it is a "simple" separation between client and sever 
code.

We added that to be able to launch a command even if the user is not logged in 
on the machine on which the server is installed. We wanted the command to be 
executed on the user's console then transfered to the server tools (on another 
machine) and the results to get back to the user's console.

But, since the current commands and the new one you're adding are only "local" 
commands, maybe it's better to use the 1.0 implementation for all the commands 
and keep the architecture we've set out in a sandbox (in case we need it 
someday).

I can also implement the command in the new way if you like.

I don't know what's the best solution...

> Data is "lost" after adding Index to config file
> ------------------------------------------------
>
>                 Key: DIRSERVER-922
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-922
>             Project: Directory ApacheDS
>          Issue Type: Bug
>    Affects Versions: 1.5.0
>         Environment: amd64
> 128M RAM
> 768 Swap
> prebuilt i386 apacheds-1.5.0
>            Reporter: Martin Marcher
>            Assignee: Pierre-Arnaud Marcelot
>             Fix For: 1.5.1
>
>
> Install Server
> add sevenseas Partition without any indexes (no property tag for indexes here 
> at all)
> start server
> connect with LDAPStudio 0.8 (do not disconnect!)
> Load o=sevenSeas SampleData
> open server.xml Config file
> copy indexes from examplePartition to sevenSeasPartition
> don't yet save the file
> stop the server
> save server.xml
> start the server gain
> LDAPStudio will not show any data under o=sevenSeas.  (Note: Do not close the 
> connection and reconnect)
> When Trying to add the data again you will find that it is still there
> as importing again throws errors.
> This is is also the case when closing connection and reopening the connection
> as well as quitting ldapstudio and restarting it
> reloading "this entry and all it's children" didn't help
> reloading schema didn't help either.
> greets
> martin

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to