gasilher.blogg.se

Primefacs icefaces usage
Primefacs icefaces usage















IceSoft says they have made enhancements which we see none looking at their code. Anyone can copy PrimeFaces and call it X Faces and offer commercial support. You are expected to fix issues, debug problems and evolve a product that you have not implemented.

primefacs icefaces usage

You must have misunderstood their feedback and 75% of your codebase now comes from PrimeFaces. Richfaces is used together with PrimeFaces and JBOSS did it by following standards. I am sure your clients did not ask you to copy PrimeFaces and call it IceFaces but fix your implementation so it could work well with competitor projects.

PRIMEFACS ICEFACES USAGE CODE

IceSoft basically solved the problem by copying the code base from PrimeFaces instead of doing real work and fixing the problem itself. The D2D approach caused integration problems with other frameworks such as PrimeFaces, Richfaces and OpenFaces. For anyone familiar with IceFaces, it has several drawbacks in its implementation. Such changes need to be made in IceFaces framework code.

primefacs icefaces usage

IceSoft says they got frequent requests from their clients to make IceFaces widgets work with PrimeFaces widgets. Based on the feedback from Prime Technology we made the decision to proceed with forking some of the project components and combining them with other components from JQuery, YUI and or ourselves to collectively form the ACE library. We need some level of confidence that these changes could be contributed back to the parent project with a reasonable chance that the code contributions would be adopted. In order to meet our support obligations and committed service level agreements, it is necessary that ICEsoft retain the ability to make code changes to an integrated technology so that we can resolve bugs and affect solutions in a timely manner for our users. After 4-5 months of discussion, we were advised that any code contributions made that related to the integration with the ICEfaces framework would ultimately not be accepted. We initially approached Prime Technology with the hope of sponsoring the PrimeFaces project and working with them to resolve some of the technical issues around a possible integration. The changes were required so the components could take advantage not only framework features such as Automatic Ajax and Ajax Push, but also so they could be incorporated in the various build and QA processes we had put in place, and to resolve some operational problems with the wide range of platforms we were committed to support (such as IE 7, WebSphere Portal …). The second conclusion reached was that successful integration was going to require code modifications and some refactoring the primefaces components.

primefacs icefaces usage

First, Primefaces had done a very good job with their 2.X offering, wrapping JQuery and YUI elements amongst others. As we investigated the possibility two things became clear. This is a good question that merits some additional explanation from our perspective.įrom late 2010 through mid 2011 one of the more frequent requests that we received from our users was to find a way to integrate elements of the jQeury and the PrimeFaces libraries so that they could work within the ICEfaces framework. One of the questions from the above dialog that we (ICEsoft) have perhaps not fully addressed already is why we felt it necessary to fork the PrimeFaces project in the first place.















Primefacs icefaces usage