myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gerhard Petracek (JIRA)" <>
Subject [jira] [Resolved] (EXTCDI-171) allow custom parameters for view-configs
Date Sun, 11 Sep 2011 22:58:09 GMT


Gerhard Petracek resolved EXTCDI-171.

       Resolution: Fixed
    Fix Version/s: 1.0.2

> allow custom parameters for view-configs
> ----------------------------------------
>                 Key: EXTCDI-171
>                 URL:
>             Project: MyFaces CODI
>          Issue Type: Improvement
>          Components: JEE-JSF12-Module, JEE-JSF20-Module
>    Affects Versions: 0.9.5
>            Reporter: Gerhard Petracek
>            Assignee: Gerhard Petracek
>             Fix For: 1.0.2
> it should be possible to extend a class annotated with @Page and annotate this class
with @Parameter.List({@Parameter(key="customParam", value="#{customBean.value1}"), ...})
> if this class is used for navigation, codi should navigate to the page which is represented
by the super-class (the class annotated with @Page) + all parameters should be added to the
requested url.
> furthermore, it should be possible to use @Parameter directly at the same view-config
class which is annotated with @Page
> as an alternative it should be possible to annotate action methods with @Parameter.
> e.g. @Parameter(on = CustomPage.class, key="customParam", value="#{customBean.value1}")
> ... this would be also an alternative to approach mentioned at the beginning. a central
class could do all mappings. however, this would reduce the possibility to use existing IDE
support and it isn't obvious at the first view that parameters will be added.

This message is automatically generated by JIRA.
For more information on JIRA, see:


View raw message