public void action(ActionEvent event) {
             InputFile inputFile = (InputFile) event.getSource();
		     if (inputFile.getStatus() == InputFile.INVALID) {
                inputFile.getFileInfo().getException().printStackTrace();
             }
        }
        

MethodBinding representing a progress listener method that will be notify the application on the percentage of the file being uploaded. The expression must evaluate to a public method that takes a single parameter of type com.icesoft.faces.component.inputfile.InputFileProgressEvent, with a return type of void.

These are some things to consider when implementing the progressListener.

• Beans which implement the progressListener must be in session scope.
• The PersistentFacesState must be set in the constructor of session bean.
• The progressListener method may invoke the executeAndRender() call on the PersistentFacesState instance, or may use the OnDemandRenderer, in order to render the page.
• The progressListener method must take a single argument of type com.icesoft.faces.component.inputfile.InputFileProgressEvent.
• From the InputFileProgressEvent's getComponent() or getSource() methods, developers may attain a reference to the InputFile component.
• If the progressListener is being invoked due to the inputFile causing a form submit (refer to the submitOnUpload attribute), then the InputFile's FileInfo object's isPreUpload() or isPostUpload() method will return true, depending if the form post is from before or after the file upload.

Historically, when the inputFile's current file upload was progressing, and the progressListener was invoked, the progressListener's bean would implement com.icesoft.faces.async.render.Renderable, and use the com.icesoft.faces.async.render.RenderManager in conjunction with the com.icesoft.faces.async.render.OnDemandRenderer, to do a server push, to update the view in the browser with the current progress. It could also invoke either PersistentFacesState.render() or PersistentFacesState.renderLater(), to accomplish the same thing.

As of ICEfaces 1.7.1, you can just set progressRender="true", and the server push will happen for you, without setting up all that glue code in the bean. You still have to set your outputProgress component's progress percent in the bean via the progressListener, and you have to enabled asynchronous mode, by setting the com.icesoft.faces.synchronousUpdate context parameter to false.

As of ICEfaces 1.8 DR#2, the RenderManager method is completely outdated, since now the inputFile requires a full JSF lifecycle for each progress event, meaning that now it automatically renders itself. Neither is it necessary to set progressRender="true", since it is true by default. It's possible to set progressRender="false", to disable the lifecycles, but that will also disable the progressListener and actionListener MethodBindings and the file settable ValueBinding, since these all happen within JSF lifecycles.

Note: The default value is true.

Space-separated list of CSS style class(es) to be applied when this element is rendered. This value must be passed through as the "class" attribute on generated markup.
Default value is iceInpFile.
Style classes used, if enabled:

• iceInpFile
• iceInpFileBtn
• iceInpFileTxt

• iceInpFile-dis
• iceInpFileBtn-dis
• iceInpFileTxt-dis

Depending on the value of submitOnUpload, the inputFile may post its enclosing form, before and/or after the file upload occurs. Possible values are:

none

File uploading will not cause the inputFile's enclosing form, and any other of the form fields, to be submitted to the server.

preUpload

The inputFile's enclosing form, and any other of the form fields, will be submitted to the server, immediately before the file uploading begins.

postUpload

The inputFile's enclosing form, and any other of the form fields, will be submitted to the server, immediately after the file uploading finishes.

preAndPostUpload

The inputFile's enclosing form, and any other of the form fields, will be submitted to the server, both before and after the file uploading takes place.

This is to support two different use cases. Applications running in synchronous mode can not make use of server push, so to depict the beginning and the ending of the file upload requires browser initiated JSF lifecycles, accomplished via form submissions. As well, for some applications, it's desirable to submit other form fields when the user clicks on the file upload button, so that they may be processed together with the uploaded file.

Note: The default value is none.