![]() ![]() ![]() Therefore the client removes it from the page and he has to refresh to get the table back (on the correct page). Because DataTableRenderer doesn't render the table (only the content) IceFaces doesn't find the table and thinks it is removed. Then IceFaces tries to find the table in order to identify the type of change (insert, replace, delete, edit. Since the data table just changes the page DataTableRenderer only renders the content inside the table. But since I still have IceFaces on some (other) pages IceFaces handles the render response phase which results in some wrong behavior. The most significant change is that the legacy ICE (Compat) components have not been brought forward into the 4.0 release. ICEfaces EE is a fully-tested and certified enterprise-grade solution ideal for companies that require a fully-supported production platform with guaranteed SLA response times. ICEfaces 4.0 is a major version release and as such adds, removes, and changes a significant number of features and APIs. I try to migrate my data table (lazy) with a paginator. This commercial version of ICEfaces 4.3 provides additional features and benefits targeted at robust and scalable enterprise application deployments. ![]() While migrating I encountered many issued related to a different JSF version, but in the end I got both running on the same page.īut I still have a some issues with some specific components. I am in the same horrible bad situation, that I am using IceFaces 3.3.0 and now have to migrate to PrimeFaces. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |