Issue #57 has been updated by Jonathan Clarke.
Hi J?r?me, I had a look at your patches. Thanks for posting them. The first one, in BeanComparator, seems pretty clear - you're handling all binary attributes specially, and removing the new String(<binary value>). This looks OK, except for one thing I'm unsure about : will bug #45 reappear? We should really write a test for that. About the second one, I am unclear as to what it's trying to do. Could you provide some explanation, maybe some comments in the code or a description in this issue? Thanks in advance, Jon ---------------------------------------- Bug #57: db2ldap : Binary attribute seems to be corrupted http://tools.lsc-project.org/issues/show/57 Author: J?r?me Schell Status: New Priority: Normal Assigned to: Category: Core Target version: I am in the process of syncing a MySQL database with an openldap directory. In the MySQL table, there is a blob containing a JPEG picture of the person. The SQL field is mapped directly to the jpegPhoto LDAP attribute like that: <pre> <result property="jpegPhoto" column="photo"/> </pre> The synchronization process is working fine except that the JPEG in the LDAP directory seems to be invalid. An export of the field is not a valid JPEG file and no LDAP browser displays the picture correctly. It seems that binary attributes should be handled differently than others. See that "forum post":http://www.velocityreviews.com/forums/t139104-ldap-character-encoding.html for information about this. The parameter "java.naming.ldap.attributes.binary" should contain a list of LDAP attributes to be handled as binary. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://tools.lsc-project.org/my/account -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.lsc-project.org/pipermail/lsc-dev/attachments/20090616/e2279534/attachment-0001.htm>
