[prev in list] [next in list] [prev in thread] [next in thread] 

List:       myfaces-dev
Subject:    [jira] [Resolved] (EXTCDI-175) introduce @ViewParam annotation for page beans
From:       "Gerhard Petracek (JIRA)" <dev () myfaces ! apache ! org>
Date:       2014-09-17 11:35:34
Message-ID: JIRA.12507023.1305224450000.54367.1410953734090 () Atlassian ! JIRA
[Download RAW message or body]


     [ https://issues.apache.org/jira/browse/EXTCDI-175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel \
]

Gerhard Petracek resolved EXTCDI-175.
-------------------------------------
    Resolution: Won't Fix

> introduce @ViewParam annotation for page beans
> ----------------------------------------------
> 
> Key: EXTCDI-175
> URL: https://issues.apache.org/jira/browse/EXTCDI-175
> Project: MyFaces CODI
> Issue Type: New Feature
> Reporter: Mark Struberg
> 
> When using the ViewConfig in CODI we not only get type safe navigation but also \
> know the 'connection' between views and their backing beans. We already support \
> annotations like @PreRenderView and likes for such beans.  We should also support \
> the direct annotation of view parameters directly in the backing beans. instead of \
> declaring the view parameters in the xhtml: <f:metadata>
> <f:viewParam id="versionParam" name="version" value="#{backingbean.versionString}" \
> required="false"/> <f:viewParam id="searchString" name="s" \
> value="#{backingbean.searchString}" required="false"/> </f:metadata>
> we can maybe use an annotation directly in the backing bean:
> @Named
> @RequestScoped
> public class Backingbean {
> @ViewParam(required=false, name="version")
> private String versionString;
> @ViewParam(required=false, name="s")
> private String searchString;
> @PreRenderView
> private void dosomeinit() {
> ...
> }
> }



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[prev in list] [next in list] [prev in thread] [next in thread]