wicket.util.upload

Protocol independent upload utilities. Copied from the Apache Jakarta Commons FileUpload project (1.1-dev, HEAD at 21st of august 2005).

The default implementation of the wicket.util.upload.FileItem FileItem interface.

After retrieving an instance of this class, you may either request all contents of file at once using DiskFileItem.get() or request an java.io.InputStream InputStream with DiskFileItem.getInputStream() and process the file without attempting to load it into memory, which may come handy with large files.
author:
   Rafal Krzewski
author:
   Sean Legassick
author:
   Jason van Zyl
author:
   John McNally
author:
   Martin Cooper
author:
   Sean C.

The default wicket.util.upload.FileItemFactory implementation.

This class represents a file or form item that was received within a multipart/form-data POST request.

After retrieving an instance of this class from a wicket.util.upload.FileUpload FileUpload instance, you may either request all contents of the file at once using FileItem.get() or request an java.io.InputStream InputStream with FileItem.getInputStream() and process the file without attempting to load it into memory, which may come handy with large files.

While this interface does not extend javax.activation.DataSource per se (to avoid a seldom used dependency), several of the defined methods are specifically defined with the same signatures as methods in that interface.

A factory interface for creating FileItem instances.

High level API for processing file uploads.

This class handles multiple files per single HTML widget, sent using multipart/mixed encoding type, as specified by RFC 1867.

How the data for individual parts is stored is determined by the factory used to create them; a given part may be in memory, on disk, or somewhere else.

High level API for processing file uploads.

This class handles multiple files per single HTML widget, sent using multipart/mixed encoding type, as specified by RFC 1867.

How the data for individual parts is stored is determined by the factory used to create them; a given part may be in memory, on disk, or somewhere else.

Low level API for processing file uploads.

This class can be used to process data streams conforming to MIME 'multipart' format as defined in RFC 1867. Arbitrarily large amounts of data in the stream can be processed under constant memory usage.

The format of the stream is defined in the following way:
multipart-body := preamble 1*encapsulation close-delimiter epilogue
encapsulation := delimiter body CRLF
delimiter := "--" boundary CRLF
close-delimiter := "--" boudary "--"
preamble := <ignore>
epilogue := <ignore>
body := header-part CRLF body-part
header-part := 1*header CRLF
header := header-name ":" header-value
header-name := <printable ascii characters except ":">
header-value := <any ascii characters except CR & LF>
body-data := <arbitrary data>


Note that body-data can contain another mulipart entity.

Abstracts access to the request information needed for file uploads.

High level API for processing file uploads.

This class handles multiple files per single HTML widget, sent using multipart/mixed encoding type, as specified by RFC 1867.

Provides access to the request information needed for a request made to an HTTP servlet.