https://issues.apache.org/bugzilla/show_bug.cgi?id=44021
--- Comment #7 from Eric Benzacar <[EMAIL PROTECTED]> 2008-03-12 08:15:24 PST --- (In reply to comment #6) > (In reply to comment #5) > > Regarding the auto-deployment of /foo: > > This is the current behaviour of Tomcat. If I manually put a war into > > /foo/abc.war and create a foo#war.xml context file, Tomcat's auto-deployer > > will > > deploy both foo/abc.war and foo/. As far as I see it, this is expected > > behaviour. > This is currently an invalid configuration. The way I see this working would > be > a foo#abc.war file in the appBase which creates/uses a foo.abc.xml context > file. 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? > > Regarding a clash of foo#bar.war and foo#bar#too.war, that is one thing > > that I > > had not considered or taken into account. I can understand that to be > > confusing. The best suggestion I can have for that is to have the > > deployment > > of foo#bar#too.war fail if there is already something that is deployed at > > foo#bar.war, In fact, I am surprised that it does not already do this. > I think this needs to work. Maybe if the files are expanded to directories > named foo#bar and foo#bar#too? This could also fix the autodeployment of foo > problem. The problem with this, however, is that if foo#bar.war is deployed, you have to assume that any path under foo/bar belongs to the foo#bar.war file. For instance, foo#bar.war might have a path as foo/bar/eric/file.jsp. This is the current way that tomcat seems to work. Similarly, it might have a file under foo/bar/too/file.jsp, which would be properly served. 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. I'm not convinced that allowing foo#bar.war to be deployed as well as foo#bar#too.war will not cause significant conflicts and errors for some people who deploy conflicting paths without realizing it. Thanks, Eric -- 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]
