: 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 that. <Context> based JNDI declarations have been documented on teh wiki for a long time ... i'm specificly questioning the recent addition suggesting that unpacking the war and editing the web.xml as a way to "configure" the Solr Home. : > i would prefer to keep this info off the wiki, or move it somewhere where : > it's more clear that it's only for people who really wnat to "HACK" on the : > solr war. (commented out in the web.xml like "path-prefix" perhaps?) : So you want to *hide* information that some users will find useful? : That doesn't seem very user friendly :-). neither is suggesting that people need to find the web.xml for their app ... i'm not suggesting we "hide" anything, i'm saying that the typical Solr user should not be expected to understand what or where a web.xml is. The type of user that is that might want to set JNDI properties directly in the web.xml is a) going to be looking at the web.xml; and b) probably already going to know that's possible to set arbitrary JNDI props that way without us telling them -- general documenting about declaring the Solr Home using JNDI (which we have) is enough. Our advanced users who "get" how WARs work don't need info like this, and it can only confuse our novice users who don't know (and don't want to know) that much about the internals of a WAR. -Hoss
