you basically want to follow the same approach used by the Seam wiki plugin architecture. There should be an article here on the seam web site, but I can't seem to find it anymore.
Anyway, the solution is to create a custom facelet resource resolver (implementing the ResourceResolver interface) which will load the xhtml pages from the whole application classpath. You install it in your web.xml like this:
<context-param> <param-name>facelets.RESOURCE_RESOLVER</param-name> <param-value>es.tsbsoluciones.platform.utils.web.ClasspathResourceResolver</param-value> </context-param>
I'm quite sure there are several posts that explain the issues involved, but again, this morning it seems I'm out of luck with the site search engine.
Thanks for the tip! I'll look into it.
Pay attention that this is only respected by Facelets for xhtml-files and is not useable for other resources like css, images and so on.