Export of Array-Attribute-Types for Apache-DS not working correctly
-------------------------------------------------------------------

                 Key: DIRSTUDIO-346
                 URL: https://issues.apache.org/jira/browse/DIRSTUDIO-346
             Project: Directory Studio
          Issue Type: Bug
          Components: studio-apacheds-configuration
    Affects Versions: 1.1.0
            Reporter: Andreas Eternach


Hi there,

i detected a problem related to array-attribute-types. When i export the 
core-schema to format Apache-DS i get following LDIF-Output for attribute 
serialNumber (which is actually an array type):

dn: m-oid=2.5.4.5, ou=attributeTypes, cn=core, ou=schema
objectclass: metaAttributeType
objectclass: metaTop
objectclass: top
m-oid: 2.5.4.5
m-name: serialNumber
m-description: RFC2256: serial number of the entity
m-equality: caseIgnoreMatch
m-substr: caseIgnoreSubstringsMatch
m-syntax: 1.3.6.1.4.1.1466.115.121.1.44

IMHO the Schama-Exporter sould add 'm-singleValue=FALSE' in case the 
xml-attribute, because the ApacheDS generates default-value m-singleValue=TRUE:

dn: m-oid=2.5.4.5, ou=attributeTypes, cn=core, ou=schema
objectclass: metaAttributeType
objectclass: metaTop
objectclass: top
m-oid: 2.5.4.5
m-name: serialNumber
m-description: RFC2256: serial number of the entity
m-equality: caseIgnoreMatch
m-substr: caseIgnoreSubstringsMatch
m-syntax: 1.3.6.1.4.1.1466.115.121.1.44
m-singleValue=FALSE
 
<attributetype oid="2.5.4.5" obsolete="false" singlevalue="false" 
collective="false" nousermodification="false">
            <aliases>
              <alias>serialNumber</alias>
            </aliases>
            <description>RFC2256: serial number of the entity</description>
            <usage>USER_APPLICATIONS</usage>
            <syntax>1.3.6.1.4.1.1466.115.121.1.44</syntax>
            <equality>caseIgnoreMatch</equality>
            <substring>caseIgnoreSubstringsMatch</substring>
 </attributetype>



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

Reply via email to