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: <9322890.1195667203105.JavaMail.jira@brutus>
Date: Wed, 21 Nov 2007 09:46:43 -0800 (PST)
From: "Emmanuel Lecharny (JIRA)" <jira@apache.org>
To: dev@directory.apache.org
Subject: [jira] Commented: (DIRSERVER-1104) Mixing Attribute value types
 results in write failures
In-Reply-To: <4141152.1195618362988.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/DIRSERVER-1104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12544535 ] 

Emmanuel Lecharny commented on DIRSERVER-1104:
----------------------------------------------

Does the trunk build ok? Of so, yes, I agree, we will have to get this issue fixed before merging bigbang into runk. Makes sense.

> Mixing Attribute value types results in write failures
> ------------------------------------------------------
>
>                 Key: DIRSERVER-1104
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-1104
>             Project: Directory ApacheDS
>          Issue Type: Bug
>          Components: core
>    Affects Versions: bigbang, 1.5.1
>            Reporter: Alex Karasulu
>            Assignee: Emmanuel Lecharny
>            Priority: Blocker
>             Fix For: bigbang
>
>         Attachments: error.log, offending.ldif
>
>
> This new bug is really serious and tricky. It has eluded us but comes out now thanks to a crazy size effect it has on Windows.  
> First a characterization of the bug.  An entry (Attributes object) may be valid and still contain an Attribute which has both byte[] and String array values.  Some may suggest that this is invalid since attributes are, according to their syntax, either binary of human readable.  However this is not the case.  The fact that an attributeType is human readable has no bearing on how the user supplies the value.  Human readable data can be provided as binary information so long as it still conforms to the syntax of the attribute.
> Here's an example entry which would cause such a failure:
>     dn: cn=person1,ou=system
>     objectClass: organizationalPerson
>     cn: person1
>     sn: sn_person1
>     seealso: cn=Good One,ou=people,o=sevenSeas
>     seealso:: Y249QmFkIEXDqWvDoCxvdT1wZW9wbGUsbz1zZXZlblNlYXM=
> This entry will cause the AttributeSerializerUtils.serialize() method to blow a ClassCastException.  Note the log of the error can be found attached to this issue.  

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