directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jacob S. Barrett (JIRA)" <>
Subject [jira] Updated: (DIRLDAP-38) Search request BER parser incorrectly parses complex filters.
Date Fri, 25 Mar 2005 02:23:24 GMT
     [ ]

Jacob S. Barrett updated DIRLDAP-38:

    Attachment: AND-OR.patch

I think this fixes it.  It isn't the most pretty.  Should probably replace the Stack with
LinkedList to get rid of the synchronizations, but I want to go play poker now.  I will post
a better fix tomorrow some time.  Thanks for your help.

> Search request BER parser incorrectly parses complex filters.
> -------------------------------------------------------------
>          Key: DIRLDAP-38
>          URL:
>      Project: Directory LDAP
>         Type: Bug
>   Components: Common
>     Versions: 0.9.0
>  Environment: NA
>     Reporter: Jacob S. Barrett
>     Assignee: Alex Karasulu
>     Priority: Blocker
>      Fix For: 0.9.0
>  Attachments: AND-OR.patch
> Using the following search from an LDAP client, like Softera's browser or OpenLDAP's
ldapsearch, search for something like the following filter:
> (& (a=A) (| (b=B) (c=C) ) )
> The resulting expression object after the BER parser is finished is:
> (& (| (c=C) (b=B) (a=A) ) )
> This is obviously not the correct expression and results in bobus results.
> I thought at first it might have been the expression object serializing to a string form
that had issue, but passing the same filter string through the commons.filter.FilterParserImpl
produces the correct expression object and the correct serialized string.
> I am attempting to debug the problem further.  If I can produce a patch I will post it,
but if someone has a better idea of what is going please tackle this.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
If you want more information on JIRA, or have a bug to report see:

View raw message