Comparison between Vaadin and ZK

Question

Does someone know of a comparison between ZK and Vaadin?

I'm especially interested which of the two is better suited for a dynamic web app (i.e. where the layout and POJOs are defined at runtime and can change at any time).

Most examples look pretty good if you have a standard POJO (with a fixed set of fields). But how do the frameworks fare if the POJO is replaced with a Map<String, Object> and I need to build the UI depending on the Map's content?

Answer 1

Both frameworks handle dynamic UI:s just fine. When choosing the framework, you should compare things like components included, number and quality of add-on components, licensing, documentation, community and so forth.

Answer 2

You find Vaadin oriented comparison/discussion here: vaadin.com/forum/-/message_boards/view_message/134071 and another one (more ZK oriented) here: jtechnoprojects.blogspot.com/2011/05/zk-vs-vaadin.html

Furthermore, regarding on your topic about Map content, I think you should be fine with Vaadin's Item interface. For example the "PropertiesItem" addon is essentially backed by a Map (java.util.Properties to be exact) and it binds directly to Vaadin Forms.