I have similar issues with my web files.
I have an (ear) application that has to be customized for different customers. In the ejb, I use the @Install tags to override the default classes, which works quite well.
I'd like to use the same functionality for the xhtml files: Having the default xhtml files in one war file and just the ones that I need to override in a second war.
For example, if a user browses to /modul/home.seam, the application should look in the second war if there is a /modul/home.xhtml and use that one if it exists. If not, it should take the one in the default war file.
Is something like that possible and how do I accomplish that?