[ 
https://issues.apache.org/jira/browse/DIRSERVER-855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12478466
 ] 

Alex Karasulu commented on DIRSERVER-855:
-----------------------------------------

Thanks for testing this out.  Emmanuel was dead on with using the case of the 
attribute ID supplied in the search.  

Yes I agree that this is not too critical.  It just annoys me personally ... 
makes the server seem somewhat flaky if it's not adhering to these unspoken 
expectations.   




> 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
>         Assigned To: Emmanuel Lecharny
>            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.

Reply via email to