Interface responsible for processing file uploads by multiple processors one after another in a chained fashion. An Apache Trinidad application could have multiple
ChainedUploadedFileProcessor
instances. A composite UploadedFileProcessor is accessible from the {@link org.apache.myfaces.trinidad.context.RequestContext}, but will be invoked automatically by the framework as needed. Developers can implement this interface and chain many of them up together using space separated class names in
trinidad-config.xml
file under
uploaded-file-processor
element. The order in which the processors will be instantated and called will be the same as how it appears inside the element.
To configure file uploads, the default instance supports three context initialization parameters :
- org.apache.myfaces.trinidad.UPLOAD_MAX_MEMORY: the maximum amount of memory that can be used in a single request to store uploaded files. (Default of 100K)
- org.apache.myfaces.trinidad.UPLOAD_MAX_DISK_SPACE: the maximum amount of disk space that can be used in a single request to store uploaded files. (Default of 2000K)
- org.apache.myfaces.trinidad.UPLOAD_TEMP_DIR: the name of a directory to store temporary files. (Defaults to the user's temporary directory)
@see org.apache.myfaces.trinidad.model.UploadedFile