> What is the execution flow of a query in sesat? A life-cycle , or thousand-foot view, diagram can be found under the javadoc for the no.search.sesat package: http://sesat.no/projects/sesat-kernel/sesat-core-api/apidocs/no/sesat/ search/package-summary.html
(Ignore the datamodel diagram underneath it as it is already out of date.) > What is the order of query transform,result handler,run handler, > run transform? The above diagram explains these except for run transform and run handler. These two are associated to the RunningQuery. The pattern in the Sesat-Kernel is that the Transformers are pre-processing, and the Handlers are post-processing. > What is the order of the result of query in sesat? The order? Maybe i've misunderstood you, but the sorted order of results is usually determined by the backend. If this is a parameter of the backend you can set up a Navigation (see the NavigationConfig and NavigationController classes) to make it easy for you to switch between sorting styles in your velocity/jsp templates. There's also documentation on this navigaton model http://sesat.no/navigation-documentation.html (careful though, this document was written while the navigation model was under implementation and may be out of date in places.It also doesn't cover the UrlGenerator and other useful new stuff). ~mck ps please keep in mind that trunk can be unstable, especially over the past 2 weeks most attention has been put the 2.18 branch. If you get into troubles it may be wise to try this branch instead. It is considered our "stable" branch now. -- "Laugh, share some happiness with the world. God knows we all have problems, believe that sometimes it pays to act like a fool to make someone else happy!" Anon | www.semb.wever.org | www.sesat.no | www.sesam.no | _______________________________________________ Kernel-development mailing list [email protected] http://sesat.no/mailman/listinfo/kernel-development
