Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Won't Fix
-
Affects Version/s: 2.0.1
-
Fix Version/s: 3.0
-
Component/s: None
-
Labels:None
-
Environment:all
Description
One of the goals of JSF2 was to improve compatibility between JSF component libraries. Apparently Icefaces cannot work together with Primefaces.
The Primefaces people point to Icefaces to get this fixed.
See http://code.google.com/p/primefaces/issues/detail?id=1829
The Primefaces people point to Icefaces to get this fixed.
See http://code.google.com/p/primefaces/issues/detail?id=1829
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
I find this statement "ace:dataTable, which has more features than the PF one" rather funny. I am an old Icefaces user your reputation of lack of compatability is unfortunatly true. At the moment my company is facing a choice to continue its Icefaces usage or migrate to PrimeFaces. Although we have more experience with Icefaces and I am the main advocate of Icefaces. Guys!!!! I am totaly out of arguments in your support!!! You are doing everything wrong.
Show
Alexander Petrov
added a comment - I find this statement "ace:dataTable, which has more features than the PF one" rather funny. I am an old Icefaces user your reputation of lack of compatability is unfortunatly true. At the moment my company is facing a choice to continue its Icefaces usage or migrate to PrimeFaces. Although we have more experience with Icefaces and I am the main advocate of Icefaces. Guys!!!! I am totaly out of arguments in your support!!! You are doing everything wrong.
As primefaces custom component updating takes some liberties with the standard JSF2 rendering cycle it is not completely feasible to support all prime-faces components directly.
Recommendation is to use the new ICEfaces 2.1 ace:dataTable, which has more features than the PF one.