directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jörg Henne (JIRA) <j...@apache.org>
Subject [jira] Updated: (DIRSERVER-694) Schema is no longer served
Date Fri, 04 Aug 2006 11:33:16 GMT
     [ http://issues.apache.org/jira/browse/DIRSERVER-694?page=all ]

Jörg Henne updated DIRSERVER-694:
---------------------------------

    Attachment: DIRSERVER-694.patch

> Schema is no longer served
> --------------------------
>
>                 Key: DIRSERVER-694
>                 URL: http://issues.apache.org/jira/browse/DIRSERVER-694
>             Project: Directory ApacheDS
>          Issue Type: Bug
>    Affects Versions: pre-1.0
>            Reporter: Jörg Henne
>         Attachments: DIRSERVER-694.patch
>
>
> Due to two problems, the schema was no longer returned from a search in 1.0-trunks:
> - the LdapDN is normalized once it hits the SchemaService and therefore no longer matched
> - the ExceptionService essentially had the same problem.
> As I considered the hard-coded subschemaSubentry DN in the ExceptionService bad design
anyway, I got rid of the check and let the SchemaService properly handle the hasEntry() call.
> Patch follows.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

Mime
View raw message