Mailing-List: contact dev-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Directory Developers List" <dev@directory.apache.org>
Message-ID: <1023272675.1216890212426.JavaMail.jira@brutus>
Date: Thu, 24 Jul 2008 02:03:32 -0700 (PDT)
From: "Pierre-Arnaud Marcelot (JIRA)" <jira@apache.org>
To: dev@directory.apache.org
Subject: [jira] Updated: (DIRSTUDIO-150) Improve error handling
In-Reply-To: <28184011.1184328246828.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/DIRSTUDIO-150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pierre-Arnaud Marcelot updated DIRSTUDIO-150:
---------------------------------------------

    Fix Version/s:     (was: 1.2.0)
                   1.3.0

Postponed.

> Improve error handling
> ----------------------
>
>                 Key: DIRSTUDIO-150
>                 URL: https://issues.apache.org/jira/browse/DIRSTUDIO-150
>             Project: Directory Studio
>          Issue Type: Improvement
>          Components: studio-ldapbrowser
>    Affects Versions: 0.8.0
>            Reporter: Stefan Seelmann
>            Assignee: Stefan Seelmann
>             Fix For: 1.3.0
>
>
> When an error occurs while quering the directory we should add the used search parameters to the error message. This would help to determine if the error is caused by the client or the server.
> Reported by ALLENW here: http://www.macupdate.com/info.php/id/24597/apache-directory-studio 
> minor: Clicking on an such an entry [with an / in DN] throws up an error that says "Error reading entry". Clicking on details shows an LDAP error code 32 - no such object. Rather than show you what LDAP Studio is trying to query, I had to hop onto the server to see what it was looking for. [That's when I discovered the major problem above.]

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