[jira] Updated: (TRINIDAD-1858) Fix fail-over bugs where session state is mutated without dirtying the Session objects

["Blake Sullivan (JIRA)" <de...@myfaces.apache.org>]

     [ https://issues.apache.org/jira/browse/TRINIDAD-1858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Blake Sullivan updated TRINIDAD-1858:
-------------------------------------

    Status: Patch Available  (was: Open)

> Fix fail-over bugs where session state is mutated without dirtying the Session objects
> --------------------------------------------------------------------------------------
>
>                 Key: TRINIDAD-1858
>                 URL: https://issues.apache.org/jira/browse/TRINIDAD-1858
>             Project: MyFaces Trinidad
>          Issue Type: Bug
>    Affects Versions: 1.2.13-core , 2.0.0.3-core
>            Reporter: Blake Sullivan
>            Assignee: Blake Sullivan
>         Attachments: jira1858Trunk.diff
>
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>
> In order for servlet engines to know which Session attributes to fail over at the end of the request, the Session tracks which attributes have had puts or removes performed on them.  This means that in order to be failed over, any change to an object tree rooted in a Session attribute must dirty the session attribute by the end of the request.  There are bugs in both the TokenCache and SessionChangeManager where they don't do this in all cases

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