You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Stefan Zoerner (JIRA)" <ji...@apache.org> on 2007/02/15 13:48:05 UTC
[jira] Created: (DIRSERVER-855) Object class "objectClass" is
called "ObjectClass" in search results
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.1
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.
Re: [jira] Commented: (DIRSERVER-855) Object class "objectClass" is called "ObjectClass" in search results
Posted by Alex Karasulu <ak...@apache.org>.
Emmanuel,
On 3/5/07, Emmanuel Lecharny <el...@gmail.com> wrote:
>
> Alex Karasulu a écrit :
>
> > 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?
>
> I don't really know when this problem appeared first.
Yeah I don't know either when the problem occurred but Stefan had
noticed the problem after releasing 1.0.1.
What we can do is
> to provide the user with the standard attribute value (ie objectClass,
> not ObjectClass), but we will have to browse the code for all the places
> where we compare an attribute type against a String without taking care
> of case sensitivity. A new method have been added in AttributeUtils to
> do that one month ago.
Oh really? Let's use it then.
I won't favor the case where the user search for, say, (OBJECTCLASS=*)
> and excpect to receive :
> dn: dc=example,dc=com
> dc: example
> OBJECTCLASS: domain
> OBJECTCLASS: extensibleObject
> OBJECTCLASS: top
Hmmm ok will this be to hard to accomplish? Is this all happening because
Rdn
class normalizes by default the attribute id?
Alex
> >
> > Thanks.
> >
> > On 3/3/07, Emmanuel Lecharny (JIRA) <ji...@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.
> >>
> >>
> >
>
>
Re: [jira] Commented: (DIRSERVER-855) Object class "objectClass"
is called "ObjectClass" in search results
Posted by Emmanuel Lecharny <el...@gmail.com>.
Alex Karasulu a écrit :
> 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?
I don't really know when this problem appeared first. What we can do is
to provide the user with the standard attribute value (ie objectClass,
not ObjectClass), but we will have to browse the code for all the places
where we compare an attribute type against a String without taking care
of case sensitivity. A new method have been added in AttributeUtils to
do that one month ago.
I won't favor the case where the user search for, say, (OBJECTCLASS=*)
and excpect to receive :
dn: dc=example,dc=com
dc: example
OBJECTCLASS: domain
OBJECTCLASS: extensibleObject
OBJECTCLASS: top
I will take care of the problem in 1.0.2 and in 1.5.0.
Emmanuel
>
> Thanks.
>
> On 3/3/07, Emmanuel Lecharny (JIRA) <ji...@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.
>>
>>
>
Re: [jira] Commented: (DIRSERVER-855) Object class "objectClass" is called "ObjectClass" in search results
Posted by Alex Karasulu <ak...@apache.org>.
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) <ji...@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.
>
>
[jira] Commented: (DIRSERVER-855) Object class "objectClass" is
called "ObjectClass" in search results
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12478346 ]
Emmanuel Lecharny commented on DIRSERVER-855:
---------------------------------------------
Partially fixed in 1.0.2 :
http://svn.apache.org/viewvc?view=rev&rev=515053
http://svn.apache.org/viewvc?view=rev&rev=515055
http://svn.apache.org/viewvc?view=rev&rev=515056
http://svn.apache.org/viewvc?view=rev&rev=515057
http://svn.apache.org/viewvc?view=rev&rev=515058
> 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.
[jira] Commented: (DIRSERVER-855) Object class "objectClass" is
called "ObjectClass" in search results
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12483653 ]
Emmanuel Lecharny commented on DIRSERVER-855:
---------------------------------------------
Is it still an issue in 1.0.2 ?
> 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.
[jira] Assigned: (DIRSERVER-855) Object class "objectClass" is
called "ObjectClass" in search results
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Lecharny reassigned DIRSERVER-855:
-------------------------------------------
Assignee: Emmanuel Lecharny
> 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.
[jira] Resolved: (DIRSERVER-855) Object class "objectClass" is
called "ObjectClass" in search results
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Lecharny resolved DIRSERVER-855.
-----------------------------------------
Resolution: Fixed
Hmmmm. This issue stayed in the "In Progess" status too long.
> 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.5.1
>
>
> 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.
[jira] Closed: (DIRSERVER-855) Object class "objectClass" is called
"ObjectClass" in search results
Posted by "Stefan Zoerner (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stefan Zoerner closed DIRSERVER-855.
------------------------------------
This has been fixed for some time and especially it works in the 1.0.2-SNAPSHOT.
> 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.5.1
>
>
> 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.
[jira] Commented: (DIRSERVER-855) Object class "objectClass" is
called "ObjectClass" in search results
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (DIRSERVER-855) Object class "objectClass" is
called "ObjectClass" in search results
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12485232 ]
Emmanuel Lecharny commented on DIRSERVER-855:
---------------------------------------------
I fixed it. Did I forgot to mark the issue 'resolved' ?
> 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.5.1
>
>
> 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.
[jira] Commented: (DIRSERVER-855) Object class "objectClass" is
called "ObjectClass" in search results
Posted by "Stefan Zoerner (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12483699 ]
Stefan Zoerner commented on DIRSERVER-855:
------------------------------------------
No, it has been fixed in 1.0.2. But the problem is still present in 1.5.0
> 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.
[jira] Updated: (DIRSERVER-855) Object class "objectClass" is
called "ObjectClass" in search results
Posted by "Stefan Zoerner (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stefan Zoerner updated DIRSERVER-855:
-------------------------------------
Fix Version/s: (was: 1.0.1)
1.0.2
Not as important as other things to get a valid 1.0.1, therefore I move it to 1.0.2
> 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.
[jira] Commented: (DIRSERVER-855) Object class "objectClass" is
called "ObjectClass" in search results
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12477929 ]
Emmanuel Lecharny commented on DIRSERVER-855:
---------------------------------------------
The returned entry will use objectClass instead of ObjectClass. For every attributes, the standard case for each attribute as specified in the schema will be used : don't expect to receive OBJECTCLASS if you do a search with (OBJECTCLASS=*).
Will be fixed in 1.0.2 and 1.5.0
> 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.
[jira] Commented: (DIRSERVER-855) Object class "objectClass" is
called "ObjectClass" in search results
Posted by "Alex Karasulu (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (DIRSERVER-855) Object class "objectClass" is
called "ObjectClass" in search results
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Lecharny updated DIRSERVER-855:
----------------------------------------
Fix Version/s: (was: 1.0.2)
1.5.1
Good enough for me :)
It's one less bug for 1.0.2, and one more for 1.5.1
> 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.5.1
>
>
> 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.
[jira] Commented: (DIRSERVER-855) Object class "objectClass" is
called "ObjectClass" in search results
Posted by "Stefan Zoerner (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12485228 ]
Stefan Zoerner commented on DIRSERVER-855:
------------------------------------------
I have just checked this bug with the current 1.5.0 SNAPSHOT (rev 523736), and it is gone. Everything works just fine. Has anybody deliberately fixed it?
> 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.5.1
>
>
> 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.
[jira] Commented: (DIRSERVER-855) Object class "objectClass" is
called "ObjectClass" in search results
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12478340 ]
Emmanuel Lecharny commented on DIRSERVER-855:
---------------------------------------------
Another step would be to return the attributes the user is waiting using the names he gave to the server in the attributes list to be returned. For instance, if the user specify that he wants OBJECTCLASS, then he adds OBJECTCLASS to the list of wanted attributes, and we return all the objectClasses using OBJECTCLASS.
> 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.
[jira] Commented: (DIRSERVER-855) Object class "objectClass" is
called "ObjectClass" in search results
Posted by "Alex Karasulu (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (DIRSERVER-855) Object class "objectClass" is
called "ObjectClass" in search results
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12478416 ]
Emmanuel Lecharny commented on DIRSERVER-855:
---------------------------------------------
well, atm, the requested attributes are returned as they were provided, except for objectClass which is treated differently, because SchemaService has been modified to handle such cases as adding missing objectClasses.
The test you added to check that the casing is respected works well for all the attributeTypes, otherwise.
Does it worth the pain to deal with people trying to insert OBJECTCLASS as an attribuetType, and expecting to get back OBJECTCLASS? I bet no. For other attributeTypes, like organizationalPerson (for instance), keeping the user's casing seems important, and in fact this is what we have currently implemented.
May be someone would dedicate a few hours writing some complete test cases to check that we respect this contract ? Anyone ?
> 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.
[jira] Commented: (DIRSERVER-855) Object class "objectClass" is
called "ObjectClass" in search results
Posted by "Stefan Zoerner (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12485234 ]
Stefan Zoerner commented on DIRSERVER-855:
------------------------------------------
This is great, Emmanuel. Thanks! Especially, because it will already work in the upcoming 1.5.0 release.
It was not a very important issue, but I definitely did not like the big "O" in the search results.
And yes, currently, the issue is marked as "In Progress".
> 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.5.1
>
>
> 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.
[jira] Commented: (DIRSERVER-855) Object class "objectClass" is
called "ObjectClass" in search results
Posted by "Stefan Zoerner (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12478434 ]
Stefan Zoerner commented on DIRSERVER-855:
------------------------------------------
I think, this is not that important. I have retested the current server, and my original issue is fixed (ObjectClass vanished).
By the way, Alex: Sun Java System Directory Server 5.2 uses the attribute names provided in the search in the results, for instance:
$ ldapsearch -b "dc=magritte" -s base "(objectClass=*)"
version: 1
dn: dc=magritte
dc: magritte
objectClass: top
objectClass: domain
$ ldapsearch -b "dc=magritte" -s base "(objectClass=*)" OBJECTCLASS DC
version: 1
dn: dc=magritte
OBJECTCLASS: top
OBJECTCLASS: domain
DC: magritte
Currently, I have not the chance to test other servers, because I am in the office. But as depicted above -- Not that important.
> 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.