You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Gerhard Petracek (JIRA)" <de...@myfaces.apache.org> on 2011/03/06 14:52:25 UTC
[jira] Created: (EXTCDI-150) ViewConfigResolver - resolving
view-configs via an api
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.getViewDescriptor(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
[jira] Resolved: (EXTCDI-150) ViewConfigResolver - resolving
view-configs via an api
Posted by "Gerhard Petracek (JIRA)" <de...@myfaces.apache.org>.
[ 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