Mailing-List: contact dev-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Directory Developers List" <dev@directory.apache.org>
Message-ID: <32703563.1154691196395.JavaMail.jira@brutus>
Date: Fri, 4 Aug 2006 04:33:16 -0700 (PDT)
From: =?utf-8?Q?J=C3=B6rg_Henne_=28JIRA=29?= <jira@apache.org>
To: dev@directory.apache.org
Subject: [jira] Updated: (DIRSERVER-694) Schema is no longer served
In-Reply-To: <25549741.1154690773909.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

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

J=C3=B6rg 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=C3=B6rg 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 n=
o longer matched
> - the ExceptionService essentially had the same problem.
> As I considered the hard-coded subschemaSubentry DN in the ExceptionServi=
ce bad design anyway, I got rid of the check and let the SchemaService prop=
erly handle the hasEntry() call.
> Patch follows.

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