Can't we do something? It's a real PITA problem and makes the server look
bad even though it is operating correctly. This was something new that
appeared right after the 1.0 release I think no?
Thanks.
On 3/3/07, Emmanuel Lecharny (JIRA) <jira@apache.org> wrote:
>
>
> [
> https://issues.apache.org/jira/browse/DIRSERVER-855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12477613]
>
> Emmanuel Lecharny commented on DIRSERVER-855:
> ---------------------------------------------
>
> Yeah, this is a nasty side effect. We have a real problem with uper/lower
> casing in x. It should be fixed in 1.5.
>
> I don't see any easy solution for 1.0.x
>
> > Object class "objectClass" is called "ObjectClass" in search results
> > --------------------------------------------------------------------
> >
> > Key: DIRSERVER-855
> > URL: https://issues.apache.org/jira/browse/DIRSERVER-855
> > Project: Directory ApacheDS
> > Issue Type: Bug
> > Components: core
> > Affects Versions: 1.0.1
> > Environment: * ApacheDS 1.0.1 (SNAPSHOT, Rev. Rev. 507868)
> > * Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_07-b03)
> > * Windows XP Professional SP2
> > Reporter: Stefan Zoerner
> > Priority: Minor
> > Fix For: 1.0.2
> >
> >
> > Currently it looks like this:
> > $ ldapsearch -h localhost -p 389 -D "uid=admin,ou=system" -w ****** -b
> "dc=example,dc=com" -s base "(objectClass=*)"
> > version: 1
> > dn: dc=example,dc=com
> > dc: example
> > ObjectClass: domain
> > ObjectClass: extensibleObject
> > ObjectClass: top
> > Although obviously not important: I would expect attribute "objectClass"
> here (as it is called in the schema). The issue arises with all entries,
> newly created ones as well.
>
> --
> This message is automatically generated by JIRA.
> -
> You can reply to this email to add a comment to the issue online.
>
>
|