Details
-
Type: Bug
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: 3.2
-
Fix Version/s: EE-3.2.0.GA, 3.3
-
Component/s: ACE-Components
-
Labels:None
-
Environment:All
-
ICEsoft Forum Reference:
Description
When the multi-part form upload is prematurely stopped, it causes several problems. First of all, trying to add the FacesMessage for the issue will cause a NPE due to trying to access the UIViewRoot's Locale when there is not yet a UIViewRoot. Secondly, the logged message can clutter production logs, and isn't particularly informative. Thirdly, the JSF lifecycle typically can't execute due to necessary form fields not being transmitted as well as the browser ceasing the request and not accepting a response, so there is no real way to inform the user of what happened.
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
There's no real working around the fact that the request is aborted and so there is no response, but it might have helped from changing the logging to happen at WARN instead of SEVERE and only when in Development mode. As well, fixing the NPE allows the Locale to be lazily evaluated at render phase, which has the benefit that if the application is some kind of config user interface where the user is specifying their locale, then the FacesMessages will be made using the newly selected locale and not the stale old one.
icefaces3 trunk
Subversion 33033