New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Request parameter map is always empty for multipart requests #136
Comments
Hmmm. It even doesn't work with PrettyFaces 3.3.3. If I remember correctly, I've already created JSF pages with upload components which were mapped with PrettyFaces. That's weird. |
Ups. Seems like this is not a bug. For Tomcat you have to set From the docs:
See: http://tomcat.apache.org/tomcat-7.0-doc/config/context.html As Glassfish and AS7 are also based on Tomcat, I guess it is the same issue there. |
I'll keep this one open because we should add this to the FAQ. |
I added this to the FAQ: https://github.com/ocpsoft/rewrite/blob/master/documentation/src/main/asciidoc/faq.asciidoc It should be avilable here as soon as Redoculous fetches the new content: |
I'm facing the same issue in Glassfish 4. Everything works perfectly if I disable PrettyFaces mapping. I've tried creating a context.xml with allowCasualMultipartParsing, and tried both deploying with my war, and saving it as a global context.xml in my domain directory. Neither one made any difference. Any other ideas on how to make this work in Glassfish? |
I'm not an expert for Glassfish, sorry. Perhaps you should ask this in the Glassfish forums. I can only tell that allowCasualMultipartParsing solves this problem for Tomcat. |
It seems like JSF postbacks don't work in multipart forms:
This is especially problematic because this
enctype
is required for JSF 2.2<h:inputFile>
.Forum reference:
http://ocpsoft.org/support/topic/problem-with-hinputfile/
I did some debugging and it seems that in case of multipart requests
HttpRewriteWrappedRequest.getParameterMap()
is always empty. Because of this JSF isn't able to find the view state request parameter and so doesn't recognize the request as a postback.As far as I can tell this is not a JSF specific problem. Instead I guess it happens with any multipart requests.
I'll create a test case to reproduce this.
The text was updated successfully, but these errors were encountered: