directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Emmanuel Lecharny <>
Subject [Schema Refactoring] Pb with AT, Collective and missing Usage
Date Sun, 22 Nov 2009 19:31:32 GMT

I had to remove the default initialization of the USAGE parameter for 
AttributeType, as we need to check that an injected AT is correct, and 
it might not be the case if it has a SUP which is not a UserApplications AT.

Let me explain the problem with some example. Let's assume we have 2 AT, 
'parent' and 'child' :

( NAME 'parent' USAGE directoryOperation )
( NAME 'child' SUP parent )

as child inherit from parent, it must have the same Usage value. In this 
case, everything is fine, as we don't have a USAGE specified, as soon as 
the USAGE does not default to UserApplications, otherwise we have an error :

( NAME 'parent' USAGE directoryOperation )
( NAME 'child' SUP parent USAGE userApplications ) /!\ Not 
allowed /!\

Now, if we don't store the Usage with a default value ( userApplications 
), we can deal with the first case, as Usage will be null. If we don't 
have a SUP, we then can default to userApplications.

Things get a bit muddier when the AT has a COLLECTIVE flag set, as now 
the USAGE *must* be userApplications.

Sadly, the description parser for such a case throw an exception when 
trying to parse :
as it does not know that the SUP has a userApplications Usage.

IMO, we have to fix this by assuming that the SUP has necessarily a 
userApplications USAGE when we have a SUP *and* a COLLECTIVE parameters 
in the string. If we don't have a SUP, then we can default USAGE to 

wdyt ?

cordialement, regards,
Emmanuel L├ęcharny

View raw message