https://issues.apache.org/bugzilla/show_bug.cgi?id=44021
--- Comment #8 from Mark Thomas <[EMAIL PROTECTED]> 2008-03-12 08:29:05 PST --- (In reply to comment #7) > Really? Why would that be an invalid configuration? I was under the > impression that the whole point of the # in the context file names was to > allow > sub-paths to the war file. Why are you looking to change that to using "." > instead? <<appBase>>/foo/abc.war is invalid The "." was a typo on my part. I meant foo#abc.xml > Now, if suddenly we allow deployment of foo#bar#too.war, you would assume that > to mean any paths under foo/bar/too would belong to the foo#bar#too.war > application, and they should all be served under that war deployment. In > which > case, you'll run into a conflict. No conflict - the spec is quite clear. The request is handled by the context with the longest context path that matches the request. Under the current code you can deploy foo.xml, foo#bar.xml and foo#bar#too.xml and it will work (providing the docBases are outside the appBase). What the current code doesn't handle, and your patch needs to fix, is dropping the equivalent wars into the appBase. The more I think about it, the more I think expansion of a#b#c.war to a dir named a#b#c is the way to fix this. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
