Mailing-List: contact dev-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Directory Developers List" <dev@directory.apache.org>
Received-SPF: pass (asf.osuosl.org: domain of aok123@bellsouth.net designates
 205.152.59.64 as permitted sender)
Message-ID: <42F37293.4020200@bellsouth.net>
Date: Fri, 05 Aug 2005 10:07:15 -0400
From: Alex Karasulu <aok123@bellsouth.net>
User-Agent: Mozilla Thunderbird 1.0.2 (Macintosh/20050317)
MIME-Version: 1.0
To: Apache Directory Developers List <dev@directory.apache.org>
Subject: Re: searchable java context implementation
References: <42F22DA9.2090308@cornell.edu>
 <1123184322.29117.6.camel@wkslx01.iktek.com>
In-Reply-To: <1123184322.29117.6.camel@wkslx01.iktek.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: quoted-printable

Hi Aaron,

I'm not sure why you want to do this with LDAP search filters.  Can you=20
clarify what you want to do here essentially abstracting it from your=20
specific application.  Meaning what additional feature are you expecting =

from a search filter?

Thanks,
Alex

Emmanuel Lecharny wrote:

>On Thu, 2005-08-04 at 11:00 -0400, Aaron Hamid wrote:
> =20
>
>>Hi,
>>
>>  I am intending to write a small service which maintains a list of "ta=
sk" entries which can be submitted, acknowledged, and searched.  The entr=
ies are going to be a fairly simple flat data structure with things like =
'submittor', 'recipient', 'submission date', 'message', etc.  Although I =
could write a search API which searches on individual fields, or perhaps =
a slightly more robust API that searches on a union of fields with implic=
it AND/OR semantics, I think it would be much more elegant to provide som=
ething like rfc 2254 ldap search s-expressions.  My question is: does any=
body know of a searchable Java context implementation?  I have tried Mirr=
orCtx, and although it does have the nice feature of persistence, it does=
 not implement a searchable API (DirContext).  Actually I think there are=
 several shallow "java" context implementations (ubiquitously seen in app=
lications like Tomcat, etc.), but I have not found any that provide searc=
h functionality.  I'm thinking something=20
>>   =20
>>
> s
> =20
>
>>imple like commons-beanutils property syntax, or OGNL property syntax.
>>
>>e.g. dirctx.bind(name, bean, ...); dirctx.search("java:/", "(|(&(color=3D=
red)(price>2)))(shape=3Dround)(name=3D*foo*)))");
>>
>>It seems like a searchable java context implementation would be useful =
in many areas.
>>   =20
>>
>
>Don't know if it's really related to a LDAP filter as described in RFC
>2254, but if you think that it is, you may look here :
>
>http://svn.apache.org/viewcvs.cgi/directory/shared/ldap/trunk/common/src=
/antlr
>
>where you will find the Filter parser and here :
>
>http://svn.apache.org/viewcvs.cgi/directory/shared/ldap/trunk/common/
>
>if you want to generate the java files and compile it.
>
>You may use it as a basis for what you want to do.
>
>However, I'm not sure that is what you want (was it you on IRC
>yesturday?). Let us know !
>
>Emmanuel L=C3=A9charny
>
>
>
>
> =20
>