Attached test case that shows issue. Run fileUploadProblem2.jsf to see issue.

From FileEntryMeta:

@Property(tlddoc="When true, the fileEntryListener will be invoked at " +
"the end of the APPLY_REQUEST_VALUES phase. Otherwise, it will be " +
"invoked just before rendering, so that the application will " +
"receive the event, regardless of whether the form has passed " +
"validation or not.",
defaultValue="false")
private boolean immediate;

The default is for the fileEntryListener to be invoked at the beginning of RENDER_RESPONSE, which won't happen if the view has navigated away to another. So try setting immediate="true" on the fileEntryListener, when using navigation. If that phase is not convenient, then try setting immediate="true" as well as using ice:setEventPhase, but I'm not sure if you can use INVOKE_APPLICATION, since it will still navigate away and I'm not sure if the FileEntryEvent will be handled first.

Added the ability for the fileEntryListener to return an outcome that, if non-null, will be used for navigation. Tested with immediate set to true and false, and navigation works. Old bean methods that have a void return type are fine, they just don't trigger navigation. Updated the FileEntryMeta @Property docs to explain it all.

icefaces3 trunk
Subversion 29780

Ported to the maintenance branch.

icefaces3-maintenance branch
Subversion 29798

For testing:

Have a bean fileEntryListener of return type void. Set immediate to true and false for uploads and make sure that still works, as before.

Have a fileEntryListener of return type String and return null, "", and a valid navigation outcome. Test with immediate set to tr and false for each of those.