directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefan Zoerner (JIRA)" <>
Subject [jira] Updated: (DIREVE-228) Schema container issue.
Date Fri, 19 Aug 2005 19:46:55 GMT
     [ ]

Stefan Zoerner updated DIREVE-228:

    Attachment: patch_DIREVE-228.txt

Here is how I fixed problem no. 1 (attachement patch_DIREVE-228.txt). This is straight forward,
I think. But I assume we have also to add conditionals in method getSubschemaEntry for the
attributes objectClass and cn attribute, they are currently returned in any situation (see
TODO location in the pach). Or do I miss something here?

It is still an open issue to me, how to handle no 2.
I need advice from the architects. Is it possible to modify schema registries after startup?
 The interfaces org.apache.ldap.server.schema offer methods to register new entries. But who
may use these components (other than during startup)?  Maybe a trivial implementation would
help Kirill (and others) in the first place (as outlined above).

Btw.: Thanks for the hint with the browser, Kirill! I would have never ever found this button.
Lucky me, you placed it on the GUI surface for the 3.1 version (I used the 2.6 browser just
for research with different client) I am spoiled ;-) 

> Schema container issue.
> -----------------------
>          Key: DIREVE-228
>          URL:
>      Project: Directory Server
>         Type: Bug
>   Components: schema
>     Versions: 0.9.2
>     Reporter: Kirill Kovalenko
>     Assignee: Alex Karasulu
>  Attachments: patch_DIREVE-228.txt
> 1) It looks like that recently implemented [1],[2] RFC3673 support (all operational attributes)
doesn't work for the schema entry. Attributes objectClasses, matchingRules, attributeTypes
are not returned when '+' special attribute is used. 
> 2) Schema container doesn't seem to provide modifyTimestamp attribute. Absence of modifyTimestamp
attribute makes it impossible for client to track schema modifications easily. 
> Here is what RFC2251 [3] says about it (section 3.2.2).
>    Servers SHOULD provide the attributes createTimestamp and
>    modifyTimestamp in subschema entries, in order to allow clients to
>    maintain their caches of schema information.
> [1]
> [2]
> [3]

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message