If you are already using tapestry-jquery why not use it's own Ajaxupload component
Sent from my iPhone On 01-Sep-2012, at 11:15 AM, Rural Hunter <ruralhun...@gmail.com> wrote: > Yes, thanks. I found that tapestry-jquery in my classpath and it intercept > the post request first sometimes. I'm wondering if there is any specific > order the request flows among several request filter chain contributed into > Tapestry HttpRequestHandler? From what I have seen, seems the order is random > among every application starts but it's fixed once the application is > started. is there any doc describe the order? > > δΊ 2012/9/1 6:08, Pavel Vodenski ει: >> The stream can only be read once, so if you have another request filter >> running before the AjaxFileUploadDecoder you'll need to make sure that it >> did not read out the stream first. >> >> - P >> >> On Fri, Aug 31, 2012 at 3:02 AM, Rural Hunter <ruralhun...@gmail.com> wrote: >> >>> I'm using Tapestry 5.3.3 and AjaxUpload comp blogged by Taha here: >>> http://tawus.wordpress.com/**2011/06/25/ajax-upload-for-**tapestry/<http://tawus.wordpress.com/2011/06/25/ajax-upload-for-tapestry/> >>> Everything works fine but there is a strange problem. Sometimes the file >>> uploaded is alwasy empty(size 0). I checked >>> AjaxFileUploadDecoderImpl.**setupUploadedFile >>> and suspected the problem is in TapestryInternalUtils.copy. So I tried to >>> read the inputstream of the request myself. But strangely I always got >>> return value -1 when I call the inputream.read when the problem happens. >>> Looks the inputstream is totally empty. I checked the request sent by >>> browser with firebug and can see the content is sent by post. Don't know >>> why I just can not read it at server end. >>> One more interesting thing is that, this problem only happens sometimes >>> after tomcat6 is recycled. Fore example, I recycle tomcat 10 times and only >>> get problem with 1 time. With that recycle, all the file upload fails. The >>> problelm persists until I recycle tomcat again. With a good recycle, the >>> problem doesn't happen at all. I tested this on several machines with >>> different tomcat versions and see the same problem on all of them. I can >>> not get any clue and hope someone could give me some light. Thanks in >>> advance. >>> >>> >>> ------------------------------**------------------------------**--------- >>> To unsubscribe, e-mail: >>> users-unsubscribe@tapestry.**apache.org<users-unsubscr...@tapestry.apache.org> >>> For additional commands, e-mail: users-h...@tapestry.apache.org >>> >>> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
