Return-Path: X-Original-To: apmail-directory-dev-archive@www.apache.org Delivered-To: apmail-directory-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id CCEDFD59B for ; Wed, 17 Oct 2012 21:22:05 +0000 (UTC) Received: (qmail 92513 invoked by uid 500); 17 Oct 2012 21:22:05 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 92458 invoked by uid 500); 17 Oct 2012 21:22:05 -0000 Mailing-List: contact dev-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Apache Directory Developers List" Delivered-To: mailing list dev@directory.apache.org Received: (qmail 92386 invoked by uid 99); 17 Oct 2012 21:22:05 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 17 Oct 2012 21:22:05 +0000 Date: Wed, 17 Oct 2012 21:22:05 +0000 (UTC) From: "Allen Zhao (JIRA)" To: dev@directory.apache.org Message-ID: <551967400.60409.1350508925464.JavaMail.jiratomcat@arcas> In-Reply-To: <1233044184.58419.1350491044993.JavaMail.jiratomcat@arcas> Subject: [jira] [Commented] (DIRSHARED-139) LdifReader missing attributes MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/DIRSHARED-139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13478403#comment-13478403 ] Allen Zhao commented on DIRSHARED-139: -------------------------------------- I understand the scenario. I tested some other LDAP apis, seems they could handle this scenario. I noticed that, internally, they convert the whole attribute to binary (if any value is binary), but when "print out", e.g. toString() or String getValue() at both entry and attribute level, it try to convert the value to string if the value is HR. Not sure this is doable in your code. BTW: I am very interesting the SchemaAware LDIFReader. But I could not find it in your API doc. If you have it, please let me know. Thanks a lot, Allen > LdifReader missing attributes > ----------------------------- > > Key: DIRSHARED-139 > URL: https://issues.apache.org/jira/browse/DIRSHARED-139 > Project: Directory Shared > Issue Type: Bug > Affects Versions: 1.0.0-M12 > Environment: Linux > Reporter: Allen Zhao > > $ cat t.ldif > dn: cn=DeviceTypes,cn=SDT,cn=prod_81,o=myconfiguration > cn: DeviceTypes > javaClassName: java.lang.String > myconfigstringvalue: P:Phone (except BlackBerry) > myconfigstringvalue:: WjpCbGFja0JlcnJ5w4LCrg== > myconfigstringvalue: 3:Internet only device > objectClass: top > objectClass: javaobject > objectClass: myconfigstringvaluedobject > Code: > LdifReader lr = new LdifReader(fileName); > while (lr.hasNext()) { > LdifEntry e = lr.next(); > System.out.println(e.toString()); > } > The attribute "myconfigstringvalue:: WjpCbGFja0JlcnJ5w4LCrg==" missed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira