Koji has a point. the <highlight> syntax has to be deprecated . All the configurations can be but into the HighlightComponent.
I shall open an issue. On Mon, Jan 4, 2010 at 9:44 AM, Chris Hostetter <hossman_luc...@fucit.org> wrote: > > : If this design is ok, I need to introduce new sub tags like > : <fragListBuilder/> and <fragmentsBuilder/> in <highlighting/> > : in solrconfig.xml. But now I wonder why the highligher settings > : are in such very original place rather than <searchComponent/>. > : > : Do we have any reason to keep <highlighting/> tag? > : Or can we move it into HighlightComponent? > > I'm not all that aware of what all is involved in the existing > <highlighting/> config options, but i suspect it was introduced *before* > search components, as a way to configure the highlighting utils that were > used by multiple request handlers ... moving all of that into init/request > params for the HighlightingComponent seems like a good idea to me -- but i > wouldn't be suprised if there were some things that make sense to leave as > independently initialized objects that are then refrenced by name, > similar to the way QParserPlugins are initialized seperately from the > QueryComponent and then refered to by name at request time. > > but as i said: i know very little about highlighting. > > > > -Hoss > > -- ----------------------------------------------------- Noble Paul | Systems Architect| AOL | http://aol.com
