Ray Sprinkle wrote:
You may have noticed that Slide updates and releases have been slow
lately. Many patches exist in bugzilla that have never been applied.
When the committers (a new one was just added to the project) become
active again, they will want these patches to fix bugs. Your part in
this involves bugzilla. See if there is already a bug in bugzilla, if
not add one. Attach your patch to the bug if one isn't already there.
I am not a committer to Slide but I use it a lot. When I come across a
bug I add it to bugzilla. Occassionally I answer questions here and try
to keep other people from tripping over the same issues that I have had.
Since I don't use the Lucene searches yet, but will be in the near
future, I personally would greatly appreciate any bug fixes that you
submit.
Thanks
You're perfectly right Ray,
I've submitted patches myself 6 months ago and they've never been
committed. After a while, I've noticed that no activity is going on the
repository and thought the project was stalled. This can lead one to
stop doing the effort of submitting patches.
Anyway, I'm glad someone is going to take over the next step and I'm
looking forward to seeing release 2.2.
regards,
Fabrice
-----Original Message-----
From: Fabrice Dewasmes [mailto:[EMAIL PROTECTED]
Sent: Monday, December 05, 2005 9:19 AM
To: Slide Users Mailing List
Subject: Re: Lucene prop search and ACLs
Max Pfingsthorn wrote:
You have to edit
src/stores/org/apache/slide/index/lucene/expressions/AbstractLuceneExpre
ssion.java.
Just add another try/catch in execute() (around lines 162-163 in svn
trunk)
try {
RequestedResource resource = createResource(uri, nodeNumber);
result.add(resource);
} catch(SlideException IGNORE) {}
max
This is also what we did but can't this be patched on svn ?
regards,
Fabrice
-----Original Message-----
From: Bart Frackiewicz [mailto:[EMAIL PROTECTED]
Sent: Monday, December 05, 2005 14:27
To: Slide Users Mailing List
Subject: Lucene prop search and ACLs
Hello,
i am using Slide 2.2pre1 (build in November) from CVS with
Lucene-based properties search. The search works fine for me except
one case:
if i search (logged in as guest user) for a phrase, which is part of a
non-accessible file, the search method response me a 400 BAD REQUEST
error:
<D:multistatus xmlns:D="DAV:">
<D:response>
<D:href>
</D:href>
<D:status>
HTTP/1.1 400 Bad Request
</D:status>
<D:responsedescription>
Access denied on /files/nur fuer root/anderedatei.txt by
user /users/guest
for action /actions/read
</D:responsedescription>
</D:response>
</D:multistatus>
I think, the search method should ignore non-accessible files. Has
someone a workaround for this?
Best regards,
Bart
--
Fabrice Dewasmes
Responsable du domaine urbanisation des systèmes d'information
[EMAIL PROTECTED]
06.89.88.65.37
--
Open Wide
14 rue Gaillon
75002 PARIS
www.openwide.fr
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]