directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pierre-Arnaud Marcelot (Commented) (JIRA)" <>
Subject [jira] [Commented] (DIRSTUDIO-764) Image Editor does not work correctly
Date Fri, 03 Feb 2012 18:13:53 GMT


Pierre-Arnaud Marcelot commented on DIRSTUDIO-764:

Hi Robert,

Thanks to your report we've identified a critical bug in the Apache Directory LDAP API which
is used by Studio 2.0.0-M1. The attribute jpegPhoto is not correctly recognized as a binary
attribute and the byte array we're getting for the image is corrupted (containing extra bytes
in the beginning).

We are working on fixing this issue and we will deliver a new milestone version of Studio
when this is fixed.

In the meantime, the workaround is to switch back to JNDI Network Provider in the connection
settings (or the global settings in the preferences).

We will also investigate the image resizing weirdness.
> Image Editor does not work correctly
> ------------------------------------
>                 Key: DIRSTUDIO-764
>                 URL:
>             Project: Directory Studio
>          Issue Type: Bug
>          Components: studio-ldapbrowser
>    Affects Versions: 1.5.3, 2.0.0-M1
>         Environment: Linux x86_64; Linux x86
>            Reporter: Robert Wolf
>            Priority: Minor
> The Image Editor does work correctly.
> LDAP object contains jpegphoto in resolution 390 x 528 points.
> In the version 1.5.3, LDAP browser can detect correct resolution and shows 390x528 and
if the image editor starts it shows description 390x528, but it shows only 322x240. Is it
bug or is it feature to show only small part of image?
> In the version 2.0.0-M1, if the jpegphoto is handled using image editor, the ldap browser
shows "invalid image" and the size is nearly as twice big as original.
> Thank you for correction to at least the same functionality as in version 1.5.3.
> Regards,
> Robert Wolf.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message