The Struts 2 framework provides built-in support for processing file uploads that conform to RFC 1867, "Form-based File Upload in HTML". When correctly configured the framework will pass uploaded file(s) into your Action class. Support for individual and multiple file uploads are provided. When a file is uploaded it will typically be stored in a temporary directory. Uploaded files should be processed or moved by your Action class to ensure the data is not lost. Be aware that servers may have a security policy in place that prohibits you from writing to directories other than the temporary directory and the directories that belong to your web application.
The Struts 2 framework leverages add-on libraries to handle the parsing of uploaded files. These libraries are not included in the Struts distribution, you must add them into your project. The libraries needed are:
If you are using Maven then you can add these libraries as dependencies in your project's pom.xml.
org.apache.struts2.interceptor.FileUploadInterceptor class is included as part of the
defaultStack. As long as the required libraries are added to your project you will be able to take advantage of of the Struts 2 fileUpload capability. Configure an Action mapping for your Action class as you typically would.
Example action mapping:
A form must be create with a form field of type file,
<INPUT type="file" name="upload">. The form used to upload the file must have its encoding type set to multipart/form-data,
<FORM action="doUpload" enctype="multipart/form-data" method="post">. The standard procedure for adding these elements is by using the Struts 2 tag libraries as shown in the following example:
Example JSP form tags:
The fileUpload interceptor will use setter injection to insert the uploaded file and related data into your Action class. For a form field named upload you would provide the three setter methods shown in the following example:
Example Action class:
The purpose of each one of these methods is described in the table below. Notice that if you have multiple file form elements with different names you would be required to have another corresponding set of these methods for each file uploaded.
The file that contains the content of the uploaded file. This is a temporary file and
The mime type of the uploaded file
The actual file name of the uploaded file (not the HTML name)
Uploading Multiple Files
As mentioned in the previous section one technique for uploading multiple files would be to simply have multiple form input elements of type file all with different names. This would require a number of setter methods that was equal to 3 times the number of files being uploaded. Another option is to use Arrays or java.util.Lists. The following examples are taken from the Showcase example application that is part sample applications you can download at http://struts.apache.org/download.cgi. For the Action mapping details see
struts-fileupload.xml in the sample application download.
Uploading Multiple Files using Arrays
multipleUploadUsingArray.jsp Notice all file input types have the same name.
Uploading Multiple Files using Lists
multipleUploadUsingList.jsp Notice all file input types have the same name.
The Struts 2
default.properties file defines several settings that affect the behavior of file uploading. You may find in necessary to change these values. The names and default values are:
Please remember that the struts.multipart.maxSize is the size limit of the whole request, which means when you uploading multiple files, the sum of their size must be below the struts.multipart.maxSize!
In order to change theses settings you define a constant in your applications
struts.xml file like so:
fileUpload interceptor has settings that can be put in place for individual action mappings by customizing your interceptor stack.
File Size Limits
There are two separate file size limits. First is
struts.multipart.maxSize which comes from the Struts 2
default.properties file. This setting exists for security reasons to prohibit a malicious user from uploading extremely large files to file up your servers disk space. This setting defaults to approximately 2 megabytes and should be adjusted to the maximum size file (2 gigs max) that your will need the framework to receive. If you are uploading more than one file on a form the
struts.multipart.maxSize applies to the combined total, not the individual file sizes. The other setting,
maximumSize, is an interceptor setting that is used to ensure a particular Action does not receive a file that is too large. Notice the locations of both settings in the following example:
There are two ways to limit the uploaded file type, declaratively and programmatically. To declaratively limit the file type a comma separated list of allowedTypes can be specified as a fileUpload interceptor param as shown in the following example:
When the uploaded file type does not match one of the MIME types specified a field error will be created as described in the next section entitled Error Messages. Programmatically limiting the file type means using the information passed in to your Action class via the
setXContentType(String contentType) method. The benefit to this type of approach would be that it's more flexible and no interceptor configuration would be needed if file sizes are keep under 2 megs.
If an error occurs several field errors will be added assuming that the action implements
com.opensymphony.xwork2.ValidationAware or extends
com.opensymphony.xwork2.ActionSupport. These error messages are based on several i18n values stored in struts-messages.properties, a default i18n file processed for all i18n requests. You can override the text of these messages by providing text for the following keys:
A general error that occurs when the file could not be uploaded
Occurs when the uploaded file is too large as specified by maximumSize.
Occurs when the uploaded file does not match the expected content types specified
Occurs when uploaded file has disallowed extension
Occurs when the upload request (as a whole) exceed configured struts.multipart.maxSize
struts.messages.upload.error.<Exception class SimpleName>
Occurs when any other exception took place during file upload process
All uploaded files are saved to a temporary directory by the framework before being passed in to an Action. Depending on the allowed file sizes it may be necessary to have the framework store these temporary files in an alternate location. To do this change
struts.multipart.saveDir to the directory where the uploaded files will be placed. If this property is not set it defaults to
javax.servlet.context.tempdir. Keep in mind that on some operating systems, like Solaris,
/tmp is memory based and files stored in that directory would consume an amount of RAM approximately equal to the size of the uploaded file.
struts.multipart.parser used by the fileUpload interceptor to handle HTTP POST requests, encoded using the MIME-type multipart/form-data, can be changed out. Currently there are two choices, jakarta and pell. The jakarta parser is a standard part of the Struts 2 framework needing only its required libraries added to a project. The pell parser uses Jason Pell's multipart parser instead of the Commons-FileUpload library. The pell parser is a Struts 2 plugin, for more details see: http://cwiki.apache.org/S2PLUGINS/pell-multipart-plugin.html. There was a third alternative, cos, but it was removed due to licensing incompatibilities.
As from Struts version 2.3.18 a new implementation of
MultiPartRequest was added -
JakartaStreamMultiPartRequest. It can be used to handle large files, see WW-3025 for more details, but you can simple set
<constant name="struts.multipart.parser" value="jakarta-stream" />
in struts.xml to start using it.