-
FEATURED COMPONENTS
First time here? Check out the FAQ!
Some people say the following:
... ZK is that it uses a proprietary Java API and a proprietary markup language...
It is reality or fiction?
This is another slender from IceFaces.
ZK is pure Java Framework, and it is compliant with both Java technologies, and Java EE technology. You can leverage the library of Java, and JEE. And ZK markup language follows the naming of XUL component, created by Mozilla.
By the way, the author is an employee of IceFaces, it is his arbitrary comment.
Regards,
Robbie
In term of JDK, I believe all Java solutions are complaint with it. The only difference is what version do they support. ZK supports JDK 1.4, 5, and later, while some might support only JDK 5 and later.
Many people overlook the advantage of JSF. Yes, it is a standard, but, if one looks further, he will find JSF has no definition of component APIs -- every JSF component uses its own proprietary API. Once a developer chose a set of JSF components, he was eventually locked to the vendor. Worse of all, JSF is a page-based architecture. Bringing the Ajax feature to this over-complicated framework creates more interoperation problem. For example, can you put RichFaces and ADF at the same page and reference the value of one component when the other component's value is changed in Ajax way? When bringing in Server Push, someone has to create so-called Push Render Management to manipulate the components. Why does a developer have to worry about this? Why can we just use them as POJO objects?
Of course, if a manager really wants JSF, we also have ZK JSF components. It helps developers to migrate gradually from a generation-old framework to the modern RIA architecture.
Regards,
Tom
Asked: 2009-04-30 01:14:55 +0800
Seen: 293 times
Last updated: May 06 '09