Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Won't Fix
-
Affects Version/s: 4.0
-
Fix Version/s: EE-4.1.0.GA
-
Component/s: ACE-Components
-
Labels:None
-
Environment:Jboss EAP 6.3.0 ace:fileEntry
-
Assignee Priority:P2
Description
If you remove the multiple="true" and other multiple file upload attributes, and place a submit button on the form, the fileEntry uploads the file without any problem.
However, with the multiple="true" and buttons which are part of this attribute on the component, the fileName is missing and it fails validation.
Note that there are multiple Content-Dispostion: values submitted for each request and that one has an empty string or filename....for example...
. ------WebKitFormBoundary7Juu0QI8HITmC6FJ
. Content-Disposition: form-data; name="example-form:file-entry"; filename="Dill Pickle Rag.pdf"
. Content-Type: application/pdf
.
.
. ------WebKitFormBoundary7Juu0QI8HITmC6FJ
. Content-Disposition: form-data; name="example-form:file-entry"; filename=""
. Content-Type: application/octet-stream
.
....
this appears to work fine in all cases except when using multiple="true" on this particular application server.
The FileEntryUpload then does not execute the captureFormField method at al ( still debugging that at the moment).
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
http://wiki.icesoft.com/display/IFEE2/JBoss+EAP+6
i used this link from QA
Testing JBoss EAP vs Tomcat 8 multiple upload shows that the issued requests are exactly the same. This rules out any client side problems. Debugging the server side shows that JBoss keeps only the last one of the uploaded fields/files that have the same name (example-form:file-entry). It seems that this is an issue with JBoss EAP 6.3 and 6.4. I could not find a bug report but there was this thread https://developer.jboss.org/thread/223085?start=0&tstart=0 which mentions a fix for this exact same issue: https://source.jboss.org/changelog/JBossWeb?cs=2179
Managed to run the showcase.war with Mojarra 2.2.13 included by specifying this JBoss context parameter:
<context-param>
<param-name>org.jboss.jbossfaces.WAR_BUNDLES_JSF_IMPL</param-name>
<param-value>true</param-value>
</context-param>
We'll consider this a Known Issue since it's a bug in JBoss itself. Will retest with JBoss EAP 7 when it's available.
Judy, how can you deploy successfully an ICEfaces 4 application on the Jboss EAP 6.3.0 who uses a modified version of JSF 2.1 ? In other words, how can I run the test in order to reproduce the issue?