Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <tomcat-user@jakarta.apache.org>
Date: Fri, 13 Aug 2004 16:01:45 +0200 (CEST)
From: =?iso-8859-1?Q?Endre_St=F8lsvik?= <Endre@Stolsvik.com>
To: Tomcat Users List <tomcat-user@jakarta.apache.org>
Subject: RE: SOLVED: How to get the context path for a web application?
In-Reply-To: <9C5166762F311146951505C6790A9CF80229BE9F@US-VS1.corp.mpi.com>
Message-ID: 
 <Pine.LNX.4.44.0408131555000.4243-100000@excalibur.intra.coretrek.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Fri, 13 Aug 2004, Shapira, Yoav wrote:

| Hi,
| And of course, since you can get the source for JSR154, there's nothing
| preventing you from adding this method and running with a custom servlet
| jar in your container.  (It's at
| http://cvs.apache.org/viewcvs.cgi/jakarta-servletapi-5/jsr154/, complete
| with a build file).

Hehe! "Forking" the JSR, that'd be a little hefty, don't you think? ;)
  Ask customers to dig up the servlet.jar from their chosen Servlet
Container, replace it with this special one, binary-patch the potentially
obfuscated class-files to implement this method, and -then- deploy the
application. Yeah, why not..!

I think I'd rather use one of the hacks suggested here, or simply
configure it in web.xml or similar, as you already suggested.

But, why wouldn't all be happy? And why isn't it simple?

Endre


---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org