myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gerhard Petracek (JIRA)" <...@myfaces.apache.org>
Subject [jira] [Commented] (MYFACES-3143) f:viewParam in templates
Date Fri, 13 May 2011 18:49:47 GMT

    [ https://issues.apache.org/jira/browse/MYFACES-3143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13033201#comment-13033201
] 

Gerhard Petracek commented on MYFACES-3143:
-------------------------------------------

it was a child of f:view. just move the usual ui:define content to the template.
use-cases: templateX should ensure that all pages always use the same view-param.
... that isn't a frequent use-case. however, besides valid use-cases there should be at least
a warning or msg. in dev. mode or exception instead of just doing nothing.

> 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

Mime
View raw message