Incremental Upload Processing Using FileEntryCallback

Table of Contents

Incremental Upload Processing Using FileEntryCallback

  Name Size Creator (Last Modifier) Creation Date Last Mod Date Comment  
HTML File 206 kB Mark Collette Jan 15, 2013 Jan 15, 2013  

The ACE FileEntry component introduces in-memory file processing. This feature is designed to provide for antivirus scanning, checksum verification or a scenario where the upload doesn't need to be saved to disk, and doing so immediately is excessive I/O.

The functionality requires that a listener bean implement FileEntryCallback to handle the incrementally uploaded bytes.
Instances of FileEntryCallback must implement:

/* Notification for upload handler when a file begins uploading.
 * fileInfo - information known about the file, before downloading the contents */
public void begin(FileEntryResults.FileInfo fileInfo);

/* We're working with chunks of bytes, as we receive them... */
public void write(byte[] buffer, int offset, int length);
public void write(int data);

/* Notification for upload handler that the file is finished. */
public void end(FileEntryResults.FileInfo fileInfo);

This example demos in-memory processing to provide an MD5 hash for an uploaded file.

Implementing FileEntryCallback

Creating our handler is the most important step of this tutorial. Everything else is just wiring up the dependant parts.

Check fileInfo.getStatus() to determine if the file has pre-failed uploading, due to too many files uploaded, an invalid file extension, or content type.
* h3. The Class Properties

The MessageDigest class is an Apache Commons class for using one-way hash algorithms like MD5 and SHA.
    private MessageDigest digest;
    private boolean md5NotFound = false;
    private List<String> extensionList = Arrays.asList("pptx","ppt","zip","etc");  // List of file types we would like to custom fail
  • The begin Method

The begin method is where your callback should request any resources it will require.
The example sets up a MessageDigest object.
    public void begin(FileEntryResults.FileInfo fileInfo) {
        try { digest = MessageDigest.getInstance("MD5"); }
        catch (NoSuchAlgorithmException e) {
            md5NotFound = true;
  • The write Methods

These methods will be passed portions of file data. If there is a chance the file will eventually be saved, the byte input should be cached here.
This example immediately computes the data as part of our hash.
    public void write(byte[] bytes, int offset, int length) {
       if (!md5NotFound) digest.update(bytes, offset, length);
    // Hash a single byte
    public void write(int i) {
        if (!md5NotFound) digest.update((byte) i);
  • The end Method

This method triggers when a file upload is complete, either successfully or with errors.

If you want to invalidate a successful upload, perhaps for certain file types, or if a users account is over quota, then this method should handle the case. It may massage the result (raising some prompts and accepting something), or possibly fail the upload for good by calling FileInfo.updateStatus(...) with the status "FileEntryStatuses.INVALID".
The example below either prints a custom FileEntryStatus for failure due to an invalid file type, a custom success FileEntryStatus, a custom MD5 error status, or, in other fail cases, lets the failed status passed to end() propagate to the view.
    // When FileEntryCallback ends for a file:
    public void end(FileEntryResults.FileInfo fileEntryInfo) {
        // We can fail the file here for invalid file type, or some other reason
	if (extensionList.contains(FilenameUtils.getExtension(fileEntryInfo.getFileName()))) {
		fileEntryInfo.updateStatus(new InvalidFileStatus(), false);
        // If the file upload was completed properly
        else if (md5NotFound) {
            // Work-around for ICEfaces 3.0.0 issue ICE-7712, where setting
            // invalidate=true will mess up the lifecycle. Instead, manually
            // invalidate the form ourselves
            fileEntryInfo.updateStatus(new EncodingNotFoundUploadStatus(), false);
            FacesContext context = FacesContext.getCurrentInstance();
        else if (fileEntryInfo.getStatus().isSuccess()) {
            fileEntryInfo.updateStatus(new EncodingSuccessStatus(getHash()), false);
        digest = null;

Adding the FileEntry Component to a Facelet Page

Nothing special is required in the facelet of this tutorial. The sample below just has some simple styling and an EL reference to the callback bean.

<ace:fileEntry id="fileEntry" callback="#{fileMD5EncodingCallback}" styleClass="ib" />
<h:commandButton styleClass="ib" value="Get MD5 Checksum" />
<div class="messages-holder"><h:messages styleClass="messages" showDetails="true" /></div>
<div style="clear:both; height:0px;">&#160;</div>

That concludes this overview of the new in-memory processing feature. If you're interested in further details of how this example works, take a look at the complete source code below; or sign up for ICEfaces training for a complete guide to this example and every feature of ICEfaces!

  Name Size Creator (Last Modifier) Creation Date Last Mod Date Comment  
HTML File 206 kB Mark Collette Jan 15, 2013 Jan 15, 2013  

Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.

© Copyright 2021 ICEsoft Technologies Canada Corp.