Turns out the globalSearch.jsp file links the command-id to its rendering. I just changed my modes.xml to have the endeca-command's id attribute by globalSearch and it works now.
But this has me wondering how one renders federated results - is there a different JSP for that? Each of the command classes is built for a specific index, and I assumed that Sesat takes the results from each, merges them, de-dups them, etc. and allows the UI to display the combined result. I must not have stumbled on the right tutorial/example for this yet - perhaps you can point me in the right direction? Any chance you have a document describing what each of the modes.xml dtd elements actually does? I am getting excited, getting close to have a functioning solution. Thanks! Brian -----Original Message----- From: Brian Frutchey Sent: Wednesday, August 12, 2009 9:06 AM To: Mck; [email protected] Subject: RE: Sesat startup feedback Working now, thanks! Only issue at this point is my "hello world" result from the EndecaSearchCommand test class doesn't seem to make it to the UI - perhaps my modes.xml result-handlers are bad? I did have to remove the regex handler as apparently it requires groups, and I just set it to ".*". Just started looking for documentation on the result-handlers as I expect that is where my problem is... Brian Frutchey Federal Solutions Architect M (703) 597-4875 E [email protected] Endeca 2100 Reston Parkway Ste 101 Reston, VA 20171 www.endeca.com find / analyze / understand -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Mck Sent: Wednesday, August 12, 2009 3:00 AM To: [email protected] Subject: RE: Sesat startup feedback > Thanks! I am now using the 2.18 branch, but when using the same > modes and views that I sent earlier, I am still getting: > > ERROR 23:02:00,578 [localhost.com:8080/ http-8080-1] > (b890115d-48fc-46b2-801a-8c6de6351013) SiteLocatorFilter: Unable to > construct AbstractEvaluatorFactory: > no.sesat.search.query.token.SolrEvaluatorFactory Like done in the sesam.com tutorial it's wise (when beginning) to turn evaluation off. Query evaluation allows you to collect (via your own plugins) metadata on words. With this metadata you then have expert rules you can run and this in turn can influence which commands to run, how to run them, etc etc. Setting up this query evaluation is explained here http://sesat.no/howto-solr-query-evaluation.html But just disabled it for now by adding to your mode (in modes.xml) evaluation="false" This will also give a vast performance improvement to requests so should always be done on any mode that is not using the evaluations results. ~mck -- "The old law about 'an eye for an eye' leaves everybody blind." Martin Luther King. Jr. | semb.wever.org | sesat.no | finn.no | _______________________________________________ Kernel-development mailing list [email protected] http://sesat.no/mailman/listinfo/kernel-development
