You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@directory.apache.org by "Alex Karasulu (JIRA)" <ji...@apache.org> on 2006/08/08 14:29:14 UTC

[jira] Closed: (DIRSERVER-694) Schema is no longer served

     [ http://issues.apache.org/jira/browse/DIRSERVER-694?page=all ]

Alex Karasulu closed DIRSERVER-694.
-----------------------------------

    Fix Version/s: 1.1.0
                   1.0-RC4
       Resolution: Duplicate

Thanks Jorg for pointing this out.

> 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
>             Fix For: 1.1.0, 1.0-RC4
>
>         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