[
https://issues.apache.org/jira/browse/MYFACES-3143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13033156#comment-13033156
]
Leonardo Uribe commented on MYFACES-3143:
-----------------------------------------
Could you provide an example so I can check it. According to the spec javadoc
(Facelets Tag Documentation) of f:metadata, it says:
"... Declare the metadata facet for this view. This must be a child of the
<f:view>. This tag must reside within the top level XHTML file for the given
viewId, or in a template client, but not in a template ...."
"... The page author is not required to use templating, but if they do, it must
be done as shown above, (or with <ui:include> in a similar manner). ...."
Based on the information provided, My conclusion is this is not a bug on
MyFaces, but maybe a test case could help to understand what's going on.
> f:viewParam in templates
> ------------------------
>
> Key: MYFACES-3143
> URL: https://issues.apache.org/jira/browse/MYFACES-3143
> Project: MyFaces Core
> Issue Type: Bug
> Components: JSR-314
> Affects Versions: 2.0.5
> Reporter: Gerhard Petracek
>
> if f:metadata and f:viewParam are in a template instead of a template-client,
> it gets parsed incorrectly. so there is no TagUnit instance for it and no
> UIPanel for f:metadata.
> -> ViewMetadata#createMetadataView doesn't work correctly (in
> ViewMetadata#getViewParameters the call root.getFacet
> (UIViewRoot.METADATA_FACET_NAME) returns a UIViewParameter directly instead
> of a Metadata node with UIViewParameter as a child).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
