Chris Hostetter wrote:
correct .. we thought we can impliment something that looked at the war
file name easily ... but then we were set straight -- there is no portable
way to do that, hence we came up with the current JNDI plan which isn't
quite as "out of the box" as we had hoped, but it has the advantage of
being possible.
Yes, I observed the discussion on the developer mailing list for a while
and was suprised to read that there isn't an easy solution for this problem.
I don't know that we'll ever be able to make configuring Solr completely
detatched from configuring the servlet container -- other then the
simplest method of putting your. Personally i don't think that should be
a major goal: a well tuned Solr installation is going to require that you
consider/configure your servlet container's heap size to meet your needs
anyway.
Good point. Currently I'm using the solr.solr.home system property and
besides the heap size it is the only Solr specific configuration I have
to do with Tomcat. So I can live with that.
just to clarify: if you only want one instance of Solr on the port, you
do't *have* to start tomcat from it's base directory
I know, I just wanted to point out that somehow Tomcat is involved in
the Solr configuration.
... you just have to
make sure the "solr" directory is in whatever the current working
directory is when you do start it.
But what if another webapp needs the server to be started from
/some/directory/it/likes ?
If the JNDI approach gets implimented, then it should make it easy for you
to specify /etc/solr (or any other directory) as your config directory
with a one line change to your tomcat configuration.
I'm looking forward to that. :-)
Thanks,
Marcus
