I checked the code of tapestry-jquery and I think it should be fine
without setting the ordering. tapestry-jquery checks the same header to
determine if it's a request from its file upload comp. Since I already
changed that header, tapestry-jquery won't process and read the reqeust
inputstream.
I think that should work too but you have to ensure that your filter is before
the tapestry-jquery filter by using before:AjaxUploadFilter for ordering.
On Sep 1, 2012, at 8:56 PM, Rural Hunter wrote:
> How would that work? will it disable both filters? One way I figured out is:
> I changed the
How would that work? will it disable both filters? One way I figured out
is: I changed the filter name and the AJAX_UPLOAD_HEADER in your code. I
think it should work. am I right?
于 2012/9/1 18:19, Taha Siddiqi 写道:
One way to handle it would be to contribute an override for "AjaxUploadFilter"
One way to handle it would be to contribute an override for "AjaxUploadFilter"
to HttpServletRequestHandler with an empty implementation of
HttpServletRequestFilter
Some thing like
public static void contributeHttpServletRequestHandler(final
OrderedConfiguration configuration,
final AjaxU
Hi Taha,
I used your comp first. Then other memeber in the team introduced
tapestry-jquery later. besides, I do more like the appearance of your
comp than he one in tapestry-jquery.
于 2012/9/1 14:29, Taha Hafeez Siddiqi 写道:
If you are already using tapestry-jquery why not use it's own Ajaxup
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 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 a
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
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 wrote:
> I'm using Tapestry 5.3.3 and AjaxUpload comp blogged by
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/
Everything works fine but there is a strange problem. Sometimes the file
uploaded is alwasy empty(size 0). I checked
AjaxFileUploadDecoderImpl.setupUploadedFile and
