icewind wrote: >Hello, > >I'm modifying the example lucene searching classes >that come with cocoon and will be packaging my version >up as a jar and using it. > >I can see that if I want to use my search components >from an XSP page, I would simply need to modify the >xsp:include tags in the xsp page to reference my >package. My question is, what is the role of the ><cocoon-indexer>, <cocoon-searcher>, <cocoon-crawler>, >and <cocoon-xml-indexer> tags in the cocoon.xconf >file? They only have logger attributes, and do not >specify the package the demo searching packages that >came with cocoon (i.e. >org.apache.cocoon.components.search.*) Are they for >logging, as the attribute names imply? Would I need to >change anything in those tags to use my custom >searching classes? >
Look into cocoon.roles files (found inside cocoon.jar), search for cocoon-indexer etc, you will find all missing pieces of the puzzle here. Basically, to define component you have to know class. Class could be default (from roles file) or custom (from class attribute). Vadim >Thanks. > > --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html> To unsubscribe, e-mail: <[EMAIL PROTECTED]> For additional commands, e-mail: <[EMAIL PROTECTED]>
