Mark, On 5/7/13 5:05 PM, Mark Thomas wrote: > On 07/05/2013 21:13, Christopher Schultz wrote: >> Mark, > >> On 5/7/13 8:54 AM, Mark Thomas wrote: >>> In an attempt to improve the situation, I have tried to document >>> a proposed expected behaviour [4]. > >> Cool. Two question: > >> 1. What is the difference between "Y/N" and "-" in a column? Y/N >> seems to mean "does not matter". Does "-" mean "does not apply"? If >> both WAR=Y and DIR=Y (column headers, not row headers) which takes >> precedence? > > Y/N means the behaviour is the same regardless of how the option is > configured. > > The meaning of '-' varied a little between the tables. I've removed > them from the first table. > > In the second and third tables '-' means "unchanged from not present". > I could have used N but I wanted to make it clearer what was changing. > >> 2. Does the order of your table indicate precedence -- for example, >> we "prefer" XML to, say, WAR or DIR, right? If so, that indicates >> that we prefer "WAR" to "DIR" > > Yes. The order is always XML, WAR, DIR. > >> but above the table you say "If both a WAR and a DIR are available >> for a web application, Tomcat will serve content from the DIR." >> which indicates the opposite. > > That is strictly for performance reasons when serving content and > doesn't affect deployment.
Perhaps I should clarify my question with an example: what happens when a WAR file is found and a DIR also exists with the same context name, but expandWars is false? Does the directory get updated with the contents of the WAR file, or does the WAR's descriptor control the deployment (subject to all the other behavior covered by your table(s)) and then (potentially old) content is served from the pre-existing DIR? Thanks, -chris
signature.asc
Description: OpenPGP digital signature
