: Some feedback from the user base. We build Solr from source (to include our
: site-specific customisations), and modify the web.xml before it goes into
I wouldn't categorize you as a basic user of Solr -- you know java,
you write customizations and you build Solr from source. You'd probably
Hi,
2008/5/31 Chris Hostetter <[EMAIL PROTECTED]>:
> I think you are being a little too presumptuious about the user base ...
> just because people use a java app doesn't mean they understand the
> internals of how a WAR or JAR file works -- nor should they.
Some feedback from the user base. W
: Adding the configuration as a comment in the actual web.xml is Ok, but
: then users should be informed that as an option (on the wiki). A user
: may never come to know that there is this comment in the web.xml which
: is an alternative way of specifying the solr home folder.
That is 100% exactl
Adding the configuration as a comment in the actual web.xml is Ok, but
then users should be informed that as an option (on the wiki). A user
may never come to know that there is this comment in the web.xml which
is an alternative way of specifying the solr home folder.
On Sat, May 31, 2008 at 6:00
: In my general experience I have seen people deploying applications in
: Tomcat by dropping in a war or by exploding the .war file into
: webapps folder. General tomcat users are more familiar with web.xml
: than server.xml. So, this is a very useful information for that class
: of users and th
On Wed, May 28, 2008 at 10:13 AM, Chris Hostetter
<[EMAIL PROTECTED]> wrote:
>
> : FWIW, Tomcat *does* support mechanisms to configure JNDI resources
> : (including the Solr Home setting) *without* modifying the WAR file
> : itself. Indeed, that was really the motivation behind having JNDI
> : res
: FWIW, Tomcat *does* support mechanisms to configure JNDI resources
: (including the Solr Home setting) *without* modifying the WAR file
: itself. Indeed, that was really the motivation behind having JNDI
: resources in the first place. Two easy approaches:
...well, yeah ... no ones disputing
: 2) The other options we have are not as easy as this (at least for a
: casual user). The most common means of deploying an app in tomcat is
: dropping the war file in the webapps folder. And the most common place
: to put in JNDI variables is web.xml
the casual user should not have to unwar and
On Tue, May 27, 2008 at 1:04 PM, Chris Hostetter
<[EMAIL PROTECTED]> wrote:
>
> : +
> : + Setting Solr Home from web.xml of solr web app
>
> 1) is this really Tomcat specific? I thought this could be done with any
> servlet container?
>
> 2) while this is another way to specify the Solr H
1) This is not tomcat specific
2) The other options we have are not as easy as this (at least for a
casual user). The most common means of deploying an app in tomcat is
dropping the war file in the webapps folder. And the most common place
to put in JNDI variables is web.xml
3) The documentation mu
: +
: + Setting Solr Home from web.xml of solr web app
1) is this really Tomcat specific? I thought this could be done with any
servlet container?
2) while this is another way to specify the Solr Home using JNDI, It
doesn't seem right to classify this as "Configuring" because it req
11 matches
Mail list logo
