Why do you use commonsFileUpload? RIFE support multipart requests out
of the box.

On Thu, Mar 6, 2008 at 3:11 PM, michaelCH <[EMAIL PROTECTED]> wrote:
>
>  Hi Garet!
>
>  I have one issue with Rife regarding POST http request.
>  I was trying to resolve it by myself but now I haven't succeeded.
>
>  The problem I have is related to file uploading.
>  I use commonsFileUpload lib to retrive the conent in the  POST request
>  and write it to a file.
>  (http://commons.apache.org/fileupload/)
>
>  When I pass the post request inside process() method in a Rife's
>  Element to the commonsFileUpload method it looks like the content in
>  the request is  'lost''. I mean the request is parssed but it's
>  handled as post with the content items inside. Of course I set:
>  setProhibitRawAccess(false).
>
>  It doesn't happen when I do it in a native servlet passing post
>  request in the same way.
>
>  Here is how I call the methods inside Rife Element:
>
>  processElement() {
>
>  setProhibitRawAccess(false);
>  request = getHttpServletRequest();
>
>  // Create a new file upload handler - commonsFileUpload method
>  ServletFileUpload upload = new ServletFileUpload();
>
>  // Parse the request  - here it return EMPTY FileItemIterator
>  unfortunately :(
>  FileItemIterator iter = upload.getItemIterator(request);
>  }
>
>  It would be very helpfull to get your opinion, cause we are developing
>  some commercial
>  service and we got stuck with that problem.
>
>  RGDS,
>  Michael Chudas.
>  >
>



-- 
Geert Bevin
Terracotta - http://www.terracotta.org
Uwyn "Use what you need" - http://uwyn.com
RIFE Java application framework - http://rifers.org
Music and words - http://gbevin.com

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"rife-users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/rife-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to