nasty problem in server side state saving

... with serialize in state disabled. I've create a small test case which shows that the attributes map is just copied over into the state. Which means that each and every Component shares exactly the same map. Any change to this map will be reflected in ALL saved states. Correct would be to

Re: nasty problem in server side state saving

Hi, Mario Ivankovits napsal(a): ... with serialize in state disabled. I've create a small test case which shows that the attributes map is just copied over into the state. Which means that each and every Component shares exactly the same map. Any change to this map will be reflected in ALL

Re: nasty problem in server side state saving

Hi! It's because the wrong constructor in api's _ComponentAttributesMap class, it's assigning the map directly: So we do agree that this needs to be fixed? Then I'll do so ... Ciao, Mario

Re: nasty problem in server side state saving

Sochor Zdeněk schrieb: Hi, Mario Ivankovits napsal(a): ... with serialize in state disabled. I've create a small test case which shows that the attributes map is just copied over into the state. Which means that each and every Component shares exactly the same map. Any change to this map

Re: nasty problem in server side state saving

Hi, [EMAIL PROTECTED] napsal(a): Sochor Zdeněk schrieb: Hi, Mario Ivankovits napsal(a): ... with serialize in state disabled. I've create a small test case which shows that the attributes map is just copied over into the state. Which means that each and every Component shares