Sounds good!
regards,
Martin
On 10/15/06, Cagatay Civici [EMAIL PROTECTED] wrote:
Yes Marting that's exactly the problem. After digging more, I've realized
that we dont need to change anything in restoreState of the component
because calling restoreAttachedState will simply return the value
Yes Marting that's exactly the problem. After digging more, I've realized that we dont need to change anything in restoreState of the component because calling restoreAttachedState will simply return the value if it's not a special wrapped type.
public Object saveState(FacesContext context) {
Hi,I'd like to discuss the latest issues about the savestate component.In order to use the component with a value of type StateHolder, restoreAttachedState-saveAttachedState is used. But using them fails with list implementations other than arraylists.
See this one;See this one;
Hi catagay,
javax.faces.component._AttachedStateWrapper is pretty much myfaces_api isn't it?
so shouldn't be used inside the savastate custom comp.
can you explain why it is failing?
Thanks!
On 10/14/06, Cagatay Civici [EMAIL PROTECTED] wrote:
Hi,
I'd like to discuss the latest issues
The problem is that a list is internally not just serialized, but
specially treated (wrapped, and then on restore you have a different
list than you had before - no good).
And that's something that Cagatay understandably doesn't want
Cagatay, how about adding an additional parameter to the