From: Remy Maucherat [mailto:[EMAIL PROTECTED] > > My proposal is to change getContext to provide the > following behaviour: > > > > Context uripath result > > ------------------------------ > > A "/" A > > A "/foo/" B > > A "/foo/bar/" C > > A "/foo/bar/xxx/" null > > > > B "/" A > > B "/foo/" B > > B "/foo/bar/" C > > B "/foo/bar/xxx/" null > > > > C "/" A > > C "/foo/" B > > C "/foo/bar/" C > > C "/foo/bar/xxx/" null > > > > I know that making this change will break a watchdog test > but my reading of the > > spec is that the current behaviour is wrong. > > Well, this breaks the spec, so this is not acceptable. The getContext > method accepts a String which is not the exact context path.
How does this break the spec? I have re-read the section on getContext several times and I don't see where it says the that the input to getContext accepts a String which is not the exact context path. Re-quoting the spec: "uripath - a String specifying the context path of another web application in the container." I read this to mean an exact match. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
