directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joerg Schaible (JIRA)" <j...@apache.org>
Subject [jira] Created: (DIRSERVER-1488) Accessing schema over JNDI delivers wrong values for mandatory/available attributes
Date Fri, 26 Mar 2010 07:08:27 GMT
Accessing schema over JNDI delivers wrong values for mandatory/available attributes
-----------------------------------------------------------------------------------

                 Key: DIRSERVER-1488
                 URL: https://issues.apache.org/jira/browse/DIRSERVER-1488
             Project: Directory ApacheDS
          Issue Type: Bug
          Components: schema
    Affects Versions: 1.5.6
            Reporter: Joerg Schaible
            Priority: Critical


When I enumerate the mandatory attributes of a class I'd expected to get an 
Attribute with an enumeration for the individual attributes:

{code:Java}
Set<String> mandatory = new HashSet<String>();
Attributes attributes = schemaCtx.getAttributes("ClassDefinition/person");
Attribute attribute = attributes.get("must");
if (attribute != null) {
    NamingEnumeration<String> enumeration = 
        (NamingEnumeration<String>) attribute.getAll();
    for (NamingEnumeration<String> values = enumeration; values.hasMore();) 
{
        mandatory.add(values.next());
    }
    JndiUtils.closeLogged(enumeration, LOG);
}
{code}

However, the result is a single entry with the value "'sn' 'cn'". According Stefan Seelmann
the LDAP classes are no longer defined correctly

In ApacheDS 1.5.5 the person object class description in cn=schema looks
like this:
( 2.5.6.6 NAME 'person' DESC 'RFC2256: a person' SUP top STRUCTURAL MUST
( sn $ cn ) MAY ( userPassword $ telephoneNumber $ seeAlso $ description
) X-SCHEMA 'core' )

In ApacheDS 1.5.6 it looks like this:
( 2.5.6.6 NAME 'person' DESC 'RFC2256: a person' SUP 'top' STRUCTURAL
MUST ( 'sn' 'cn' ) MAY ( 'userPassword' 'telephoneNumber' 'seeAlso'
'description' ) X-SCHEMA 'core' )

This is not correct according to RFC4512 and JNDI doesn't seem to be
flexible enough to parse this syntax.


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


Mime
View raw message