[richfaces-issues] [JBoss JIRA] Updated: (RF-10978) Richfaces 4.0 Final fileUpload incomptible with Primefaces 2
Justin Nauman (JIRA)
jira-events at lists.jboss.org
Tue Jul 19 12:51:23 EDT 2011
[ https://issues.jboss.org/browse/RF-10978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Justin Nauman updated RF-10978:
-------------------------------
Attachment: component_test.zip
This example is based upon the RichFaces maven simpleapp archetype.
The RichBean just has a listener that puts file information to the console to ensure it is working.
If you remove the primefaces dependency it will work. Note: I have in there currently the most recent Primefaces release, this issue DOES still fail on the stable releases as well.
> Richfaces 4.0 Final fileUpload incomptible with Primefaces 2
> ------------------------------------------------------------
>
> Key: RF-10978
> URL: https://issues.jboss.org/browse/RF-10978
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: compatibility, component-input
> Affects Versions: 4.0.0.Final
> Reporter: Matt Choate
> Fix For: 4.1.0.Final
>
> Attachments: component_test.zip
>
>
> Including the Primefaces 2 library along with Richfaces 4.0 Final causes the Richfaces fileUpload component to break. In the JBoss logs this message appears when rendering the page with the component:
> "JSF1091: No mime type could be found for file fileUploadProgress. To resolve this, add a mime-type mapping to the applications web.xml"
> Also when monitoring the HTTP traffic in Fiddler I see this entry over and over. Appears to be stuck in some loop
> /lsweb/rfRes/fileUploadProgress.jsf?ln=org.richfaces&rf_fu_uid_alt=0.712090154203886
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the richfaces-issues
mailing list