> The WAR file need not be executable I think you're using a different definition of executable than I am. I'm not thinking about the executable bit.
I'm just thinking from the perspective of the file being an object that contains instructions which are executed as opposed to configuration which is parsed. I'm thinking from an overall security perspective, not focused on the executable bit.
