Jan,
This looks good to me.
I have patches ready to go for TC4 and TC5. They are based on the
existing code but implement the spirit of Bill's proposed solution and
add handling for crossContext.
I'll give people a little longer in case they want to add to this
discussion and then I'll
Jan,
Jan Luehe wrote:
Hi Mark,
snip
I agree the current javadocs of ServletContext.getContext() are
ambiguous, and I agree we need to present this case to the
Servlet EG. Maybe there is a small chance to have this resolved
in the Servlet 2.5 timeframe ...
I think it would be more useful to
At 18:20 27/11/2005 +, you wrote:
Bill Barker wrote:
I can't really dispute the interpretation of
the spec, but the change is likely to break many more webapps then it fixes :(.
I thought this too. However, I think we should
implement the spec as is. If we start relaxing
it here, then
Hi Mark,
Mark Thomas wrote On 11/24/05 11:34,:
All,
I have been looking at bug 13040 and reviewing the current
getContext() implementation. I saw Remy's comment from some time ago
when fixing some related bugs
(http://marc.theaimsgroup.com/?l=tomcat-devm=106008981803343w=2)
that this
Bill Barker wrote:
I can't really dispute the interpretation of the spec, but the change is
likely to break many more webapps then it fixes :(.
I thought this too. However, I think we should implement the spec as
is. If we start relaxing it here, then where else do we relax it? If
other
Mark Thomas wrote:
The complications I referred to in the SSI commit are:
1. The definition of uripath says it is a context path which for the
root context would be . In the method description it says uripath
must always start with /. This is not consistent.
2. The definition of uripath
