BTW, opened the following spec issue:
https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=904
Though since the spec is somewhat vague on this topic, perhaps the
implementations can take advantage of this to provide more flexible
solutions (eg. honor extensions in FACELETS_VIEW_MAPPINGS)? It seems
like with the introduction of the new .view.xml/XML-style Facelets
processing support this is going to be fairly important to address.
Andy
On 10/29/10 4:21 PM, Andy Schwartz wrote:
Gang -
Both MyFaces and Mojarra currently assume/require the file extension
".xhtml" for composite component resources. This seems overly
restrictive. Composite component authors should be able to use other
file extensions - eg. ".view.xml", or, as we would like to do here:
".jsf".
What do folks think about introducing spec language that requires the
JSF implementations to check for composite component resources under
any extensions specified via the "javax.faces.FACELETS_VIEW_MAPPINGS"
context parameter?
Or, if we start looking into jar-specific configuration, it might be
interesting to allow such extensions to be specified on a per-resource
library basis.
Thoughts?
Andy