You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Mark Struberg (JIRA)" <de...@myfaces.apache.org> on 2010/07/09 01:15:51 UTC

[jira] Commented: (EXTCDI-2) view access scope

    [ https://issues.apache.org/jira/browse/EXTCDI-2?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12886547#action_12886547 ] 

Mark Struberg commented on EXTCDI-2:
------------------------------------

not sure if we should keep the old name @AccessScoped for the annotation. 

Basically it's really doing the same as the respective Orchestra scope. The extension to the View is necessary due to the introduction of Ajax handling (an Ajax request hitting only 1 bean would otherwise lead to loosing all other beans of a page).

> view access scope
> -----------------
>
>                 Key: EXTCDI-2
>                 URL: https://issues.apache.org/jira/browse/EXTCDI-2
>             Project: MyFaces CODI
>          Issue Type: New Feature
>          Components: JEE-JSF12-Module, JEE-JSF20-Module
>            Reporter: Gerhard Petracek
>
> this scope is similar to the access scope of orchestra.
> we have to support ajax requests (also for jsf 1.2 extensions) - so all beans used in a view will be available in the next view or 1-n requests to the same (original) view.
> annotation: @ViewAccessScope

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.