You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Leonardo Uribe (JIRA)" <de...@myfaces.apache.org> on 2008/10/09 02:19:44 UTC
[jira] Commented: (MYFACES-2001) wrong referenced scope test for
managed beans with scope 'none'
[ https://issues.apache.org/jira/browse/MYFACES-2001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12638150#action_12638150 ]
Leonardo Uribe commented on MYFACES-2001:
-----------------------------------------
Checking the jsf 1.1 mr1 spec section 5.3.1.3 says this:
" ...... It is an error for a managed bean created through this facility to have a property that points at an object stored in a scope with a (potentially) shorter life span. Specifically, this means, for an object created with the specified <managed-beanscope>, then <value> evaluations can only point at created objects with the specified managed bean scope:
none -- none
application -- none, application
session -- none, application, session
request -- none, application, session, request
.........."
So, according to the spec the code is ok (the behavior wanted is not allowed). By this reason, this issue is closed as invalid.
> wrong referenced scope test for managed beans with scope 'none'
> ---------------------------------------------------------------
>
> Key: MYFACES-2001
> URL: https://issues.apache.org/jira/browse/MYFACES-2001
> Project: MyFaces Core
> Issue Type: Bug
> Components: General
> Affects Versions: 1.1.5, 1.1.6, 1.2.0, 1.2.2, 1.2.3, 1.2.4
> Reporter: Paul Pogonyshev
>
> I get the following exception:
> Property space references object in a scope with shorter lifetime than the target scope none
> for a managed bean with scope 'none'. It sets a property to a bean in request scope. However, request scope lifetime should not be viewed as 'shorter' than 'none'. This is observed on 1.1.5, but quick check suggests that relevant source code part is the same in SVN trunk.
> As I see, check in isInValidScope() is incorrect for cases when targetScope is null or 'none'. In this case it should always return true regardless of valueScope.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.