myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Martin Marinschek (JIRA)" <...@myfaces.apache.org>
Subject [jira] Commented: (MYFACES-1850) component attributes problem with server side state saving with "serialize in state" = false
Date Fri, 04 Apr 2008 20:05:24 GMT

    [ https://issues.apache.org/jira/browse/MYFACES-1850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12585735#action_12585735
] 

Martin Marinschek commented on MYFACES-1850:
--------------------------------------------

This is very dangerous; it's good you fix it. Simon's comment is still true, however. Generally,
for references to JSF objects, this will not be a problem, cause they will implement the StateHolder-interface.
Couldn't we serialize everything which is a reference-type and not a JSF-internal class, instead
of serializing the full tree? Would this perform well? Could this be done in a central place?

regards,

Marti n

> component attributes problem with server side state saving with "serialize in state"
= false
> --------------------------------------------------------------------------------------------
>
>                 Key: MYFACES-1850
>                 URL: https://issues.apache.org/jira/browse/MYFACES-1850
>             Project: MyFaces Core
>          Issue Type: Bug
>          Components: General
>    Affects Versions: 1.1.5, 1.2.2
>            Reporter: Mario Ivankovits
>            Assignee: Mario Ivankovits
>            Priority: Critical
>
> When using server side state saving with "serialize state in view"=false all the saved
states for the same view contains a shared reference to the component attribute map.

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


Mime
View raw message