You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Aleksander Adamowski (JIRA)" <ji...@apache.org> on 2009/01/07 18:18:44 UTC
[jira] Created: (DIRSERVER-1302) Exception error message unhelpful
when adding attributeType and objectClass with colliding names
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.9
Reporter: Aleksander Adamowski
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.
Re: [jira] Created: (DIRSERVER-1302) Exception error message unhelpful when adding attributeType and objectClass with colliding names
Posted by Alex Karasulu <ak...@gmail.com>.
Excellent - thanks for correcting this in JIRA.
Alex
On Wed, Jan 7, 2009 at 12:18 PM, Aleksander Adamowski (JIRA) <
jira@apache.org> wrote:
> 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.9
> Reporter: Aleksander Adamowski
>
>
> 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.
>
>
[jira] Closed: (DIRSERVER-1302) Exception error message unhelpful
when adding attributeType and objectClass with colliding names
Posted by "Kiran Ayyagari (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (DIRSERVER-1302) Exception error message unhelpful
when adding attributeType and objectClass with colliding names
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Lecharny updated DIRSERVER-1302:
-----------------------------------------
Fix Version/s: (was: 1.5.5)
2.0.0-RC1
Postponed to 2.0.0-RC1
> 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.
[jira] Updated: (DIRSERVER-1302) Exception error message unhelpful
when adding attributeType and objectClass with colliding names
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Lecharny updated DIRSERVER-1302:
-----------------------------------------
Affects Version/s: (was: 1.5.9)
1.5.4
Fix Version/s: 1.5.5
> 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: 1.5.5
>
>
> 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.