How does AribaWeb compare to other Open Source UI Frameworks?
Although AW predates nearly all currently popular open source web frameworks, it shares an interesting combination of virtues with many of them: • Like Java Server Faces (JSF), Tapestry and Wicket, AribaWeb is a deeply component-oriented framework, and, like Wicket, AW transparently manages component server state. AW’s model of template/class binding is most similar to that of Tapestry. • Like Google Web Toolkit (GWT), ZK, and Echo2, AribaWeb enables creating AJAX applications without writing JavaScript, and like ZK and Echo2, AW’s “Auto AJAX” approach is server-based. • Like ZK, AribaWeb enables less source code to implement many UIs (and offers the ability to inline component logic in the UI template, if desired). • Like Ruby on Rails, Django, and Grails, AribaWeb provides a full stack for implementing database applications, and supports a dynamic scripting language (Groovy, in the case of AW) for conveniently expressing application logic. In addition to combining all these attribute
