The following issue has been updated:

    Updater: Florian G. Haas (mailto:[EMAIL PROTECTED])
       Date: Mon, 31 Jan 2005 5:42 PM
    Comment:
Patch to forrest-core.xconf to enable Avalon components required by Lucene. 
This is copied from the example xconf in the "lucene" block of a current Cocoon 
checkout.
    Changes:
             Attachment changed to forrest-core.xconf.20050201.patch
    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://issues.cocoondev.org//browse/FOR-431?page=history

---------------------------------------------------------------------
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: Unassigned
   Priority: Major

    Project: Forrest
 Components: 
             Core operations
   Versions:
             HEAD

   Assignee: 
   Reporter: Florian G. Haas

    Created: Mon, 31 Jan 2005 5:40 PM
    Updated: Mon, 31 Jan 2005 5:42 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

Reply via email to