noep, haven't looked at that stuff in a while.

-igor

On Tuesday, February 16, 2010, Andreas Maza <[email protected]> wrote:
> Thanks for that quick response, igor. I created now a very basic and (bad
> ,-) implementation of FileItemFactory, does not write to disk and doesn't
> spawn threads.
>
> With respect to using common-fileupload on GAE, I read about fileupload's
> new Streaming API. However, I have currently no clue how to integrate it
> with Wicket. Do you have any hints for that?
>
> thanks,
> andr
>
>
>
>
> On Tue, Feb 16, 2010 at 7:51 PM, Igor Vaynberg <[email protected]>wrote:
>
>> MultipartServletWebRequest has a constructor that allows you to pass
>> in your own fileitemfactory
>>
>> WebRequest has a newMultipartWebRequest that you can override to
>> create a multipartservletwebrequest with your own fileitemfactory...
>>
>> -igor
>>
>> On Tue, Feb 16, 2010 at 10:21 AM, A. Maza <[email protected]> wrote:
>> > Hello,
>> >
>> > I trying to implement a file upload for my wicket application, which
>> should
>> > be deployed on Google App Engine (GAE). Since GAE does not allow to spawn
>> > new threads, I cannot make use of DiskFileItem due to its use of
>> > FileCleaner.
>> >
>> > The problem is that a DiskFileItem gets instantiated in the
>> > MultipartServletWebRequest, which results in an AccessControlException
>> even
>> > before the submit method is called (which would allow to parse the
>> request
>> > by hand)
>> >
>> > Thus, I would like to ask if anyone has a hint how to deal with that
>> problem
>> > and avoid the instantiation of DiskFileItem?
>> >
>> > Thanks a lot in advance,
>> >
>> > andr
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: [email protected]
>> > For additional commands, e-mail: [email protected]
>> >
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
>>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to