https://issues.apache.org/bugzilla/show_bug.cgi?id=44021
Eric Benzacar <[EMAIL PROTECTED]> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |[EMAIL PROTECTED]
--- Comment #5 from Eric Benzacar <[EMAIL PROTECTED]> 2008-03-06 06:38:14 PST
---
Hi Mark,
Sorry for the delay in getting back to you on this; I hadn't receive the
automated notif from Bugzilla for some reason, so I didn't see you had
commented on this.
To address your concerns of my patch; I didn't have a set of specs to follow,
so I tried to do what I thought would make the most sense, and attempt to
replicate the current behaviour of Tomcat.
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.
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.
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. 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.
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]
