[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [equinox-dev] Possible bug in ServiceTracker
- From: Niclas Hedhman <niclas@xxxxxxxxxxx>
- Date: Tue, 23 May 2006 10:43:59 +0800
- Delivered-to: firstname.lastname@example.org
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:from:to:subject:date:user-agent:references:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:message-id:sender; b=nm8y0nrphGY+A4wdABfND88ZhlwkKIqWQafZYpfOQFh5Ge2Uot6IvTimR4MGi+nz/XS4uIB/22b7gfBccgcxYYRI2m1YdGDeOMyMoN04EOZ9x67cNHKegMrpnUpQO03mIxajc6d1Zw0dhPqAAl+BkBvexqzgQUg/GpxTX1XnXNE=
- User-agent: KMail/1.8.3
On Monday 22 May 2006 23:22, Thomas Watson wrote:
> It looks like you have an extra space in you filter string before the last
> String filterString = "(" + Constants.OBJECTCLASS + "=" +
> Content.class.getName() + " )";
> We do not trim the trailing spaces on the string when doing string
> matching. It may be nice to trim the trailing spaces but I'm not sure if
> that is allowed by the spec.
Extra eyeballs indeed do a lot of difference. I guess one stares oneself blind
after a while.
I checked the spec as well, the spaces are significant in the value, but
leading and trailing spaces in the key must be ignored (p. 31).
Thanks a lot, and sorry for the noise...