Underlying problem
------------------
p2fs must publish templates to the webapp root

Why this is a problem
---------------------
This prevents us from deploying CMS as a WAR.  Also, the webapp
directory name is hard-coded, and therefore brittle.  Finally,
depending on the security model of the servlet container, we may not
be able to write to the webapp directory.

How to fix it
-------------
Currently, TemplateResolver only looks in one directory when searching
for templates.  Since the default templates live in
webapps/ROOT/packages/content-section/templates, the Template Resolver
uses that directory.  Therefore, dynamically published templates must
be written to that directory in order to be found.  One solution is to
extend Template Resolver to use two paths - one for default templates
and one for dynamic templates.  Then, the directory for dynamic
templates could be outside of the webapp root.  

Thanks to Dan for pointing out the problem and the possible solution.