I'll just allow the user to pass in the port via a param for now.
Thx!
On Tue, Sep 29, 2009 at 4:13 PM, Mark Miller wrote:
> Unfortunately, because they don't want you counting on access to the
> servlet request due to embedded Solr and what not, to get that type of
> info you have to override a
Unfortunately, because they don't want you counting on access to the
servlet request due to embedded Solr and what not, to get that type of
info you have to override and use your own SolrDispatchFilter:
protected void execute( HttpServletRequest req, SolrRequestHandler
handler, SolrQueryRequest
Yah, I just found it, and was going to reply to my own message with
that exactly!
My next question is how to get the port the request was on?
On Tue, Sep 29, 2009 at 4:01 PM, Mark Miller wrote:
> Jason Rutherglen wrote:
>> Howdy,
>>
>> I was wondering what the best way is to access the current
>
Jason Rutherglen wrote:
> Howdy,
>
> I was wondering what the best way is to access the current
> instance of CoreContainer? It seems like the only way to do this
> is to extend CoreAdminHandler. I'd prefer a way via a way to
> access CoreContainer from SolrCore or RequestHandlerBase.
>
> The use c
Howdy,
I was wondering what the best way is to access the current
instance of CoreContainer? It seems like the only way to do this
is to extend CoreAdminHandler. I'd prefer a way via a way to
access CoreContainer from SolrCore or RequestHandlerBase.
The use case is, I want to implement a SearchHa
