directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gunther Lochstampfer (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DIRSTUDIO-428) Same Name for attribute type and objectclass
Date Tue, 02 Dec 2008 19:18:44 GMT

    [ https://issues.apache.org/jira/browse/DIRSTUDIO-428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12652463#action_12652463
] 

Gunther Lochstampfer commented on DIRSTUDIO-428:
------------------------------------------------

   http://www.ietf.org/rfc/rfc2252.txt says only: 

Schema developers MUST NOT create object class definitions whose
   names conflict with attributes defined for use with LDAP in existing
   standards-track RFCs.

or

Schema developers MUST NOT create attribute definitions whose names
   conflict with attributes defined for use with LDAP in existing
   standards-track RFCs.

but i defined my very own classes and attribute types which do not conflict with standard
names ... or OID's

and this works very fine in openldap and zOS ldap or Tivoly directory, so in my understanding
it is a bug


> Same Name for attribute type and objectclass
> --------------------------------------------
>
>                 Key: DIRSTUDIO-428
>                 URL: https://issues.apache.org/jira/browse/DIRSTUDIO-428
>             Project: Directory Studio
>          Issue Type: Bug
>          Components: studio-schemaeditor
>    Affects Versions: 1.3.0
>         Environment: windows xp and vista
>            Reporter: Gunther Lochstampfer
>
> given a class
> objectclass ( 1.3.6.1.4.1.25977.1.1.1.2.5 
> 	NAME 'racfClass' 
> 	DESC 'Abbildung einer RACF Resourceklasse z.B. G000401' 
> 	SUP RRContainer 
> 	STRUCTURAL 
> 	MUST racfClass 
> 	MAY ( cn $ racfResourceMember ) 
>  )
> and attribute type
> attributetype ( 1.3.6.1.4.1.25977.1.1.1.1.31 
> 	NAME 'racfClass' 
> 	DESC 'racfClass' 
> 	EQUALITY caseIgnoreMatch 
> 	ORDERING caseIgnoreOrderingMatch 
> 	SUBSTR caseIgnoreSubstringsMatch 
> 	SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 
>  )
> studio complains about alias already in use by another item ... 
> for your investigation my superior class
> objectclass ( 1.3.6.1.4.1.25977.1.1.1.2.1 
> 	NAME 'RRContainer' 
> 	DESC 'Standard Container, erweitert um Beschreibung und Status' 
> 	SUP top 
> 	STRUCTURAL 
> 	MUST cn 
> 	MAY ( description $ rr-status ) 
>  )
> this works under openldap and ldap z/OS

-- 
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