[jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-1654) ManagedEntityIdentityInterceptor does not clear values in conversation context

[Gavin King (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBSEAM-1654?page=all ]

Gavin King closed JBSEAM-1654.
------------------------------

    Fix Version/s: 2.0.0.CR1
       Resolution: Done
         Assignee: Gavin King

Fixed in CVS, please test my fix and let me know...

> ManagedEntityIdentityInterceptor does not clear values in conversation context
> ------------------------------------------------------------------------------
>
>                 Key: JBSEAM-1654
>                 URL: http://jira.jboss.com/jira/browse/JBSEAM-1654
>             Project: JBoss Seam
>          Issue Type: Bug
>    Affects Versions: 2.0.0.BETA1
>            Reporter: Wolfgang Schwendt
>         Assigned To: Gavin King
>            Priority: Critical
>             Fix For: 2.0.0.CR1
>
>
> The method  entityRefsToIds() of org.jboss.seam.persistence.ManagedEntityIdentityInterceptor is called after control returns from the intercepted target method.   It iterates over the fields of the target object and saves the values of certain field in the conversation context.  However, the curent implementation as of Seam 2.0.0.Beta1 saves only non-null values.       This has the implication that when a previous invocation of this interceptor already saved a non-null value of a field in the conversation context, but a subsequent invocation of the target method sets this field in the target object to null, the old saved value in the conversation context won't be cleared. From the user perspective, this leads to  an unexpected "caching behavior" of an old field value.
> See more detailed discussion at http://www.jboss.com/index.html?module=bb&op=viewtopic&t=113258&postdays=0&postorder=asc&start=0
> It appears to be an issue that should be investigated, because it fundamentally affects the use of stateful components in Seam.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira