directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefan Seelmann (JIRA)" <>
Subject [jira] Resolved: (DIRSTUDIO-150) Improve error handling
Date Sat, 28 Mar 2009 15:58:50 GMT


Stefan Seelmann resolved DIRSTUDIO-150.

    Resolution: Fixed

- The used search parameters are logged to the "Search Logs" view
- The error dialog shows the whole stack trace 

> Improve error handling
> ----------------------
>                 Key: DIRSTUDIO-150
>                 URL:
>             Project: Directory Studio
>          Issue Type: Improvement
>          Components: studio-ldapbrowser
>    Affects Versions: 0.8.0
>            Reporter: Stefan Seelmann
>            Assignee: Stefan Seelmann
>             Fix For: 1.4.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:

> 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.

View raw message