Message:
The following issue has been closed.
Resolver: David Crossley
Date: Mon, 31 Jan 2005 6:40 PM
Thanks, i applied your patch, and also fixed a minor typo there and in the
cocoon source.
---------------------------------------------------------------------
View the issue:
http://issues.cocoondev.org//browse/FOR-431
Here is an overview of the issue:
---------------------------------------------------------------------
Key: FOR-431
Summary: "Could not find component for role" when using Lucene search
Type: Bug
Status: Closed
Priority: Major
Resolution: FIXED
Project: Forrest
Components:
Core operations
Fix Fors:
HEAD
Versions:
HEAD
Assignee:
Reporter: Florian G. Haas
Created: Mon, 31 Jan 2005 5:40 PM
Updated: Mon, 31 Jan 2005 6:40 PM
Environment: Tested on Debian Sarge with Linux 2.6.8 and JDK 1.4.2_01
Description:
When using Lucene-based searching, the following error occurs whenever
"/lucene-search.html" is requested:
Internal Server Error
Message: null
Description: No details available.
Sender: org.apache.cocoon.servlet.CocoonServlet
Source: Cocoon Servlet
Request URI
lucene-search.html
cause
Could not find component for role:
[org.apache.cocoon.components.search.LuceneCocoonSearcher]
(Key='org.apache.cocoon.components.search.LuceneCocoonSearcher')
request-uri
/lucene-search.html
This is due to a misconfiguration in Forrest's Cocoon xconf file
(main/webapp/WEB-INF/xconf/forrest-core.xconf).
The problem only affects Lucene *searching*; indexing works fine.
This issue also blocks FOR-246.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.cocoondev.org//secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
