[
https://issues.apache.org/jira/browse/EXTCDI-171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13087309#comment-13087309
]
Gerhard Petracek commented on EXTCDI-171:
-----------------------------------------
also see https://issues.apache.org/jira/browse/EXTCDI-216
> allow custom parameters for view-configs
> ----------------------------------------
>
> Key: EXTCDI-171
> URL: https://issues.apache.org/jira/browse/EXTCDI-171
> Project: MyFaces CODI
> Issue Type: Improvement
> Components: JEE-JSF12-Module, JEE-JSF20-Module
> Affects Versions: 0.9.5
> Reporter: Gerhard Petracek
> Assignee: Gerhard Petracek
>
> 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: http://www.atlassian.com/software/jira
