[
https://issues.apache.org/jira/browse/SOLR-4792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13686984#comment-13686984
]
Noble Paul commented on SOLR-4792:
----------------------------------
bq. W1 gives the flexibility of choosing a servlet container, and upgrading it
independently of the application
it gives flexibility as well as it adds complexity to deployment. Every shop
has a preference on the web container they use and this leads to an explosion
of the permutations possible. This leads to confusion on how to upgrade things,
how to add libs to classpath etc. When someone posts a question as to how to do
'x' in appserver 'y' we will be scrambling to get a copy of that appserver and
reproducing the situation
bq. W3 leaves completely out of scope webserver configuration from the
application.
This is a valid point. But the Solr is not a regular webserver. It just needs a
subset of properties which webservers normally expose. We probably will only
have a handful of configurable properties for Solr (from the app/webserver side)
bq.Also, depending how the webapp components are declared (servlets, filters)
things can get messy.
We always don't need a webserver. The entire play web framework is written
without a servlet container. Even Solr does not need a servlet container. It is
happy as long as it can expose itself through an HTTP interface. I personally
believe Servlet Container is an overkill for Solr.
AFAIK ElasticSearch does not ship as a .war . Not shipping a .war adds to a lot
of simplicity .
> stop shipping a war in 5.0
> --------------------------
>
> Key: SOLR-4792
> URL: https://issues.apache.org/jira/browse/SOLR-4792
> Project: Solr
> Issue Type: Task
> Components: Build
> Reporter: Robert Muir
> Assignee: Robert Muir
> Fix For: 5.0
>
> Attachments: SOLR-4792.patch
>
>
> see the vote on the developer list.
> This is the first step: if we stop shipping a war then we are free to do
> anything we want.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
