directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Karasulu (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DIRSERVER-855) Object class "objectClass" is called "ObjectClass" in search results
Date Tue, 06 Mar 2007 14:01:35 GMT

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

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

Interesting idea regarding using the user supplied attributes list.  I wonder if other servers
respect this and return the attribute ID as it was asked for.  However note that for the most
general case where no requested attribute is supplied (all userApplication attributes are
returned) we still have the problem.  I guess this is a cute feature to have ... sounds appealing
at first but I think just making sure for now that attribute Ids are returned as given on
add and modify add/replace operations is preserved.

> 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.


Mime
View raw message