RE: [EXTERNAL] - Re: custom search component process method not called

2017-06-30 Thread Chris Hostetter
: It works ok for me now. Both cores execute as expected. : The ${solr.core.name} resolves correctly for both cores. As in I get the right name for each. Is still something I shouldn't do? No -- you're fine. That property is implicitly defined for all Solr cores, precisely for the type of

RE: [EXTERNAL] - Re: custom search component process method not called

2017-06-30 Thread Steve Pruitt
It works ok for me now. Both cores execute as expected. The ${solr.core.name} resolves correctly for both cores. As in I get the right name for each. Is still something I shouldn't do? -S -Original Message- From: Chris Hostetter [mailto:hossman_luc...@fucit.org] Sent: Friday, June 3

RE: [EXTERNAL] - Re: custom search component process method not called

2017-06-30 Thread Steve Pruitt
Sigh. Best way to find a stupid mistake is post it. I had this... explicit 10 saveStateComponent Instead of this explicit 10 saveStateComponent mailto:erickerick...@gmail.com] Sent: Friday, Jun