: This bothers me too. I find it really strange that Solr's entry-point
: is a servlet filter instead of a servlet.
it traces back to the need for it to decide when to handle a request and
when to let it pass through (to a later filter, a servlet or a JSP)
this is the only way legacy support
I was thinking, maybe we should write a patch to fix this issue.
For instance by making a dispatch servlet (with a "core" parameter or
request attribute) that would act the same way as the filter but
provide a cross context addressable entry point.
What do you think ?
Jerome
On Wed, Dec 17, 200
Maybe there's an 'internal query' concept in j2ee that could be a workaround ?
I'm not really a j2ee expert ..
Jerome.
On Wed, Dec 17, 2008 at 5:09 PM, Smiley, David W. wrote:
> This bothers me too. I find it really strange that Solr's entry-point is a
> servlet filter instead of a servlet.
>
>
This bothers me too. I find it really strange that Solr's entry-point is a
servlet filter instead of a servlet.
~ David
On 12/17/08 12:07 PM, "Jérôme Etévé" wrote:
Hi all,
In solr.xml ( /lucene/solr/trunk/src/webapp/web/WEB-INF/web.xml
),it's written that
"It is unnecessary, and potentia
Hi all,
In solr.xml ( /lucene/solr/trunk/src/webapp/web/WEB-INF/web.xml
),it's written that
"It is unnecessary, and potentially problematic, to have the SolrDispatchFilter
configured to also filter on forwards. Do not configure
this dispatcher as FORWARD."
The problem is that if f
