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: <1753420867.9901267265046042.JavaMail.jira@brutus.apache.org>
Date: Sat, 27 Feb 2010 10:04:06 +0000 (UTC)
From: "Kiran Ayyagari (JIRA)" <jira@apache.org>
To: dev@directory.apache.org
Subject: [jira] Closed: (DIRSERVER-1302) Exception error message unhelpful
 when adding attributeType and objectClass with colliding names
In-Reply-To: <494499734.1231348724419.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-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kiran Ayyagari closed DIRSERVER-1302.
-------------------------------------

    Resolution: Fixed

The parent issue DIRSERVER-1301 has been fixed in the trunk

> Exception error message unhelpful when adding attributeType and objectClass with colliding names 
> -------------------------------------------------------------------------------------------------
>
>                 Key: DIRSERVER-1302
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-1302
>             Project: Directory ApacheDS
>          Issue Type: Bug
>          Components: schema
>    Affects Versions: 1.5.4
>            Reporter: Aleksander Adamowski
>             Fix For: 2.0.0-RC1
>
>
> This is a follow-up to DIRSERVER-1301.
> When performing the following schema modification, due to a collision between attribute type and object class name there is a NamingException thrown:
> ########### 
> version: 1 
> dn: cn=schema 
> changetype: modify 
> add: attributeTypes 
> attributeTypes: ( 1.3.6.1.4.1.18060.0.4.3.2.1 
>         NAME 'ship' 
>         DESC 'a reference to a ship' 
>         EQUALITY distinguishedNameMatch 
>         SYNTAX 1.3.6.1.4.1.1466.115.121.1.12 
>         SINGLE-VALUE 
>  ) 
> - 
> add: objectClasses 
> objectClasses: ( 1.3.6.1.4.1.18060.0.4.3.3.1 
>         NAME 'ship' 
>         DESC 'An entry which represents a ship' 
>         SUP top 
>         STRUCTURAL 
>         MUST cn 
>         MAY ( description ) 
>  ) 
> objectClasses: ( 1.3.6.1.4.1.18060.0.4.3.3.2 
>         NAME 'port' 
>         DESC 'An entry which represents a port' 
>         SUP top 
>         STRUCTURAL 
>         MUST cn 
>         MAY ( description $ ship ) 
>  ) 
> - 
> ########### 
> However, the NamingException in such case doesn't give any hint about the real cause of the problem (name collision):
> javax.naming.directory.NoSuchAttributeException: attributeType w/ OID 1.3.6.1.4.1.18060.0.4.3.3.1 not registered! 
> at org.apache.directory.server.schema.registries.DefaultAttributeTypeRegistry.lookup(DefaultAttributeTypeRegistry.java:198) 
> at org.apache.directory.server.core.schema.ObjectClassImpl.getMayList(ObjectClassImpl.java:104) 
> at org.apache.directory.server.utils.AttributesFactory.getAttributes(AttributesFactory.java:393) 
> at org.apache.directory.server.utils.AttributesFactory.getAttributes(AttributesFactory.java:74) 
> at org.apache.directory.server.core.schema.SchemaSubentryModifier.addSchemaObject(SchemaSubentryModifier.java:188) 
> ...
> The exception should be made more informative.

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