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] Resolved: (EXTCDI-150) ViewConfigResolver - resolving view-configs via an api
Date Sun, 06 Mar 2011 15:43:25 GMT

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

Gerhard Petracek resolved EXTCDI-150.
-------------------------------------

    Resolution: Fixed

> ViewConfigResolver - resolving view-configs via an api
> ------------------------------------------------------
>
>                 Key: EXTCDI-150
>                 URL: https://issues.apache.org/jira/browse/EXTCDI-150
>             Project: MyFaces CODI
>          Issue Type: New Feature
>          Components: JEE-JSF12-Module, JEE-JSF20-Module
>            Reporter: Gerhard Petracek
>            Assignee: Gerhard Petracek
>
> currently it's required to use ViewConfigCache directly for manually using information
about a view-config.
> it should be possible to use it e.g. like:
> @Inject
> private ViewConfigResolver  viewConfigResolver; 
> //...
> this.viewConfigResolver.getViewConfig(MyPage.class).getViewId();
> therefore we have to move (and rename) some methods of ViewConfigEntry and PageBeanConfigEntry
to the api package

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message