[
https://issues.apache.org/jira/browse/EXTCDI-175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13102285#comment-13102285
]
Gerhard Petracek commented on EXTCDI-175:
-----------------------------------------
since it's annotation based, we have to provide the following approaches
#1 @RequestParam for view-controllers - manual injection before @InitView ->
for errors we might need e.g. an additional context which provides more details
than FacesContext#isValidationFailed
later we can think about:
#2 @Inject has to be used if it should be used outside of a view-controller ->
lazy injection outside of the corresponding lifecycle-phase -> might be too
complex
> 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 is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
