Re: RES: FileUploadField usage changed in 1.4 rc-1?

2008-11-25 Thread Martin Makundi
This seems to result in org.apache.wicket.util.io.SerializableChecker$WicketNotSerializableException: Unable to serialize class: org.apache.wicket.util.io.DeferredFileOutputStream I must implement the detach() method for the dummy fileUpload model: form.add(fileUploadField = new

RES: FileUploadField usage changed in 1.4 rc-1?

2008-11-19 Thread Bruno Cesar Borges
Yes, you need to set a Model object into FileUploadField. :-) Bruno -Mensagem original- De: Martin Makundi [mailto:[EMAIL PROTECTED] Enviada em: quarta-feira, 19 de novembro de 2008 14:33 Para: users@wicket.apache.org Assunto: FileUploadField usage changed in 1.4 rc-1? Hi! My

Re: RES: FileUploadField usage changed in 1.4 rc-1?

2008-11-19 Thread Erik van Oosten
Yeah, I run into the same thing. Just pass FileUploadField an empty model: new ModelFileUpload() Regards, Erik. Bruno Cesar Borges schreef: Yes, you need to set a Model object into FileUploadField. :-) Bruno -- Erik van Oosten http://www.day-to-day-stuff.blogspot.com/

Re: RES: FileUploadField usage changed in 1.4 rc-1?

2008-11-19 Thread Martin Makundi
Strange quirk.. someone removed the preceding hack from within. Is there some flaw in the FileUploadFIeld design? ** Martin 2008/11/19 Erik van Oosten [EMAIL PROTECTED]: Yeah, I run into the same thing. Just pass FileUploadField an empty model: new ModelFileUpload() Regards, Erik.