Eleni Tsigka a écrit : > Well, I use myFaces through seam (of JBOSS). I think that the status > of jsf is stored server-side. I cant't think how I could have > configured it to be stored client-side (if so it is my unintented > mistake). I don't that these data should be stored client-side. > I tried the code shown in my previous e-mail, and it partially works. > The valueChangeListener works fine and gives me the file to upload. > The obvious problem is that when the form is reshown (after a > potential validation error), if the user doesn't browse the file to > upload again, the valueChangeListener returns null. So I can't be sure > which is the desirable file. > > Do you have something else in mind, that I can't understand about > getting the actual value from the UIComponent. > > > Thanks again, > Elenh Have not tested deeply fileupload, but it seems then that developper choose the option to only care about the content of the last upload (null) and forget the past. It's always the question to ask yourself, does an empty file upload mean 'keep previous upload' or does it mean 'remove previous upload' :). If you are not happy with it's current behaviour, you can still create your own fileupload component that keeps it's state and is a bit more complex (eg, with an added checkbox that say 'file XYZ.aaa already uploaded, keep it?'). It's not that difficult to create custom JSF components.
