https://issues.apache.org/bugzilla/show_bug.cgi?id=44021
--- Comment #6 from Mark Thomas <[EMAIL PROTECTED]> 2008-03-11 15:27:09 PST --- (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. > 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. > Please let me know how you expect Tomcat to behave in the above circumstance, > and I'll see if I can update my patch for that. Done. See above ;) > I will still be working on > patching 6.0.14 however; I expect that my updates should be easily > transferrable to the 6.0.16 branch by someone a little more knowledgable of > Tomcat's internal intracacies. That's fine. The code hasn't changed much, if at all. When you get this working, I'll port it to the latest 6.0.x -- 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]
