Hola,

> request, I can find out that someone used the solr1 path to get to me
> (but that's to late for config type stuff that needs to happen in
> init()).

That but... clause is very important.  From what I understand, the
Servlet EG discussed this long and hard, many times, over many months,
before arriving at the current compromise.  There are also other
considerations (mod_rewrite comes to mind) that affects this
discussion.

Anyways, we're not going to change the spec, we're getting off-topic. 
>From my experience supporting Tomcat, approaches relying on the app's
context path or disk path are fragile at best.  The getResource
approaches (either ServletContext or classloader-based) are solid,
work well.  The JNDI approach is also solid and works well.  Other
approaches, like having a server-wide config file periodically
reloaded and used by all WARs, are also (marginally) OK.  None is a
zero-configuration approach, but all are fairly close, and easy for
both the developer to develop and the server admin to maintain.  We
could pick one, or we could develop our own thing...

Yoav

Reply via email to