You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Werner Punz (JIRA)" <de...@myfaces.apache.org> on 2010/03/02 16:14:27 UTC

[jira] Created: (EXTSCRIPT-78) Scope changing on managed bean fails

Scope changing on managed bean fails
------------------------------------

                 Key: EXTSCRIPT-78
                 URL: https://issues.apache.org/jira/browse/EXTSCRIPT-78
             Project: MyFaces Extensions Scripting
          Issue Type: Sub-task
            Reporter: Werner Punz
            Assignee: Werner Punz




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


[jira] Resolved: (EXTSCRIPT-78) Scope changing on managed bean fails

Posted by "Werner Punz (JIRA)" <de...@myfaces.apache.org>.
     [ https://issues.apache.org/jira/browse/EXTSCRIPT-78?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Werner Punz resolved EXTSCRIPT-78.
----------------------------------

    Resolution: Fixed

> Scope changing on managed bean fails
> ------------------------------------
>
>                 Key: EXTSCRIPT-78
>                 URL: https://issues.apache.org/jira/browse/EXTSCRIPT-78
>             Project: MyFaces Extensions Scripting
>          Issue Type: Sub-task
>            Reporter: Werner Punz
>            Assignee: Werner Punz
>


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


[jira] Commented: (EXTSCRIPT-78) Scope changing on managed bean fails

Posted by "Werner Punz (JIRA)" <de...@myfaces.apache.org>.
    [ https://issues.apache.org/jira/browse/EXTSCRIPT-78?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12840204#action_12840204 ] 

Werner Punz commented on EXTSCRIPT-78:
--------------------------------------

as it seems the scope is lost somewhere in the code, it should be detected by the annotation scanner but then it seems to me that it is lost somewhere between the scan and the refresh.
The refresh part only drops the beans and leaves the generation again to the runtime to get a fresh instance.


> Scope changing on managed bean fails
> ------------------------------------
>
>                 Key: EXTSCRIPT-78
>                 URL: https://issues.apache.org/jira/browse/EXTSCRIPT-78
>             Project: MyFaces Extensions Scripting
>          Issue Type: Sub-task
>            Reporter: Werner Punz
>            Assignee: Werner Punz
>


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


[jira] Commented: (EXTSCRIPT-78) Scope changing on managed bean fails

Posted by "Werner Punz (JIRA)" <de...@myfaces.apache.org>.
    [ https://issues.apache.org/jira/browse/EXTSCRIPT-78?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12840205#action_12840205 ] 

Werner Punz commented on EXTSCRIPT-78:
--------------------------------------

ok this is weird, the managed bean scope itself is set in our annotation scan part so the scope change should be there...


> Scope changing on managed bean fails
> ------------------------------------
>
>                 Key: EXTSCRIPT-78
>                 URL: https://issues.apache.org/jira/browse/EXTSCRIPT-78
>             Project: MyFaces Extensions Scripting
>          Issue Type: Sub-task
>            Reporter: Werner Punz
>            Assignee: Werner Punz
>


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