[ 
https://issues.apache.org/jira/browse/DIRSTUDIO-1167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17262272#comment-17262272
 ] 

Stefan Seelmann commented on DIRSTUDIO-1167:
--------------------------------------------

Fixed here: 
https://github.com/apache/directory-studio/commit/dfed72919c1018dc73e4ace51c4b508239bd32e2

Problem was that there was a single global object for the quick search that was 
shared across all connections. I don't know why I implemented it like that 12 
years ago...

> Quick Search does not switch target host when changing connections
> ------------------------------------------------------------------
>
>                 Key: DIRSTUDIO-1167
>                 URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1167
>             Project: Directory Studio
>          Issue Type: Bug
>          Components: studio-ldapbrowser
>    Affects Versions: 2.0.0-M12
>         Environment: Windows 7 x64, Java 8u151.
>            Reporter: Gabriel Sherrod
>            Priority: Major
>              Labels: patch, usability
>             Fix For: 2.0.0-M16
>
>
> 1). Create 2 connections, 1 against serverA and 1 against ServerB.
>  2). Perform a quick search (any kind of search) in ServerA, results are 
> displayed for ServerA.
>  3). Now switch to ServerB connection and perform same quick search. Results 
> are displayed for ServerB.
>  4). Now switch back to ServerA to view results. The connection is for 
> ServerA, but the quick search in ServerA is pointing to ServerB.
>  5). If I make a change to a quick search record in ServerA connection, it 
> changes the record in ServerB!
> This created a huge problem for me when I was comparing a test and production 
> server. My execution by connection should have been test, but the results for 
> Test Quick Search acted upon the production server.  It was also returning 
> the results from the wrong server in the Quick Search after switching 
> connections.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to