Details
-
Type: Bug
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: 4.0.BETA
-
Fix Version/s: 4.0
-
Component/s: Sample Apps
-
Labels:None
-
Environment:Icefaces 4 trunk, Myfaces 2.2.2, All browsers, Tomcat 7 r40726
-
Assignee Priority:P2
-
Affects:Documentation (User Guide, Ref. Guide, etc.), Compatibility/Configuration
-
Workaround Exists:Yes
-
Workaround Description:Application should isolate the ace:fileEntry component into it's own form to avoid this issue with MyFaces 2.2.2.
Description
When using the slider to change file size a console error appears and the file size is not updated:
Console error:
clientError: The form with the id example-form has an input file element, but is not a multipart form
http://localhost:8080/showcase/javax.faces.resource/jsf.js.jsf?ln=javax.faces&v=4_0_0_140407
Line 1
Steps to reproduce:
Build showcase in Icefaces 4 with Myfaces 2.2.2 libs.
Navigate to ace:fileEntry > Validation.
Move the slider to the right to increase file size.
Console error will appear and the file size will not be updated.
Console error:
clientError: The form with the id example-form has an input file element, but is not a multipart form
http://localhost:8080/showcase/javax.faces.resource/jsf.js.jsf?ln=javax.faces&v=4_0_0_140407
Line 1
Steps to reproduce:
Build showcase in Icefaces 4 with Myfaces 2.2.2 libs.
Navigate to ace:fileEntry > Validation.
Move the slider to the right to increase file size.
Console error will appear and the file size will not be updated.
During submit Myfaces 2.2.2 verifies (in the bridge) if the form containing the file input entry has the correct encoding type. If it's not multipart/form-data encoded it will throw an exception without an explanatory message.