[
https://issues.apache.org/jira/browse/SOLR-2586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13048220#comment-13048220
]
David Smiley commented on SOLR-2586:
------------------------------------
Well I respectfully disagree with you Yonik. I think a WAR file is enough to
provide for a production setting, and it should be enough for any Java webapp.
I'm not aware of any *serious* bugs in servlet engines that would truly warrant
recommendation against using them instead of the version of Jetty provided in
/example/. By serious, I mean two things: One is a bug requiring a patch, not
simply a configuration modification that we can easily tell users to make when
they go to production. Second, this bug must actually be a serious bug, not
just technically be a bug. If it's some arcane encoding issue that is only
going to actually trigger a real problem in some small fraction of cases, then
I don't think that's serious -- I think instead we simply tell users about it
and let them take whatever action they choose (e.g. choose another servlet
engine if it matters to them, or do nothing if they are not impacted). For the
ease of operational administration (especially for those with no Java
expertise), going with a Linux RPM (or similar package system) or Windows
Tomcat install with Service registry startup/shutdown hooks, is a lot better.
*If* I'm in the minority and those in power want to actually condone the
"/example/" setup as a production ready installation, then I think this
directory should be renamed to something like "/server/", and further
instructions should be provided on starting it and stopping it with the
operating system for at least Linux.
> example work & logs directories needed?
> ---------------------------------------
>
> Key: SOLR-2586
> URL: https://issues.apache.org/jira/browse/SOLR-2586
> Project: Solr
> Issue Type: Improvement
> Components: Build
> Reporter: David Smiley
> Priority: Minor
>
> Firstly, what prompted this issue was me wanting to use a git solr mirror but
> finding that git's lack of empty-directory support made the "example" ant
> task fail. This task requires examples/work to be in place so that it can
> delete its contents. Fixing this was a simple matter of adding:
> {code:xml}
> <mkdir dir="${example}/work" /><!-- in case not there -->
> {code}
> Right before the delete task.
> But then it occurred to me, why even have a "work" directory since Jetty will
> apparently use a temp directory instead. -- try for yourself (stdout snippet):
> bq. 2011-06-11 00:51:26.177:INFO::Extract
> file:/SmileyDev/Search/lucene-solr/solr/example/webapps/solr.war to
> /var/folders/zo/zoQJvqc9E0076p0THiri+k+++TI/-Tmp-/Jetty_0_0_0_0_8983_solr.war__solr__k1kf17/webapp
> On my Mac, this same directory was used for multiple runs, so somehow Jetty
> or the VM figures out how to reuse it.
> Since this "example" setup isn't a *real* installation -- it's just for
> demonstration, arguably it should not contain what it doesn't need.
> Likewise, perhaps the empty example/logs directory should be deleted. It's
> not used by default any way.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
