[richfaces-issues] [JBoss JIRA] (RF-10978) Richfaces 4.0 Final fileUpload incomptible with Primefaces 2
Brian Leathem (Updated) (JIRA)
jira-events at lists.jboss.org
Wed Oct 5 14:40:16 EDT 2011
[ https://issues.jboss.org/browse/RF-10978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Leathem updated RF-10978:
-------------------------------
Fix Version/s: 4.1.0.CR1
(was: 4.1.0.Tracking)
Forum Reference: http://community.jboss.org/message/604023, http://community.jboss.org/message/613883#613883 (was: http://community.jboss.org/message/604023, http://community.jboss.org/message/613883#613883)
> 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.CR1
>
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the richfaces-issues
mailing list