Apache Wicket与Apache Click [英] Apache Wicket vs Apache Click

问题描述

Apache Wicket和Apache Click有什么区别?是否维护Apache Click?最新版本似乎是从2008年11月开始谢谢阿基里斯(Achilleas)

What is the difference between Apache Wicket and Apache Click? Is Apache Click maintained? The latest release seems to be from Nov 2008 Thanks Achilleas

推荐答案

Click是积极开发的，最近已毕业为Apache顶级项目.目前，它正在迁移到其新域: http://click.apache.org .迁移完成后，将发布下一个版本2.1.0.

Click is actively developed and has recently graduated as an Apache Top Level Project. It is currently moving to its new domain at: http://click.apache.org. Once the migration is complete the next version, 2.1.0, will be released.

在比较Click和Wicket之前，请注意我是Apache Click的提交者，但是几年前对Wicket进行了评估，因此对它的工作原理有一个很好的了解.

Before comparing Click and Wicket do note that I am a committer at Apache Click but have evaluated Wicket a couple of years ago so have a fairly good idea of how it works.

点击是无状态框架，而Wicket是有状态的.在Click中，每个请求都将重新创建页面和组件，在Wicket中，页面和组件将存储在会话中，并在后续请求中重新使用.

Click is a stateless framework while Wicket is stateful. In Click, pages and components are recreated each request, in Wicket the pages and components are stored in the session and reused in subsequent requests.

Wicket用于构建复杂的应用程序(例如台式机)，在其中为您存储和管理所有GUI状态.单击是用于较传统的Web应用程序，在这种应用程序中，呈现页面几乎不需要状态.如果需要存储状态，则必须通过在会话中添加/删除状态来自己进行管理.值得一提的是，Wicket支持无状态页面，而Click支持有状态页面，但这并不是这些框架的标准.

Wicket is meant for building complex applications (think desktop), where all the GUI state is stored and managed for you. Click is meant for the more traditional web applications where little to no state is necessary to render a page. If you need to store state you have to manage it yourself by adding/removing it from the session. Its worth mentioning that Wicket provides support for stateless pages and Click supports stateful pages, however this isn't the norm for these frameworks.

另一个区别是，在Click控件中，控件知道如何呈现自己，因此您不必在页面模板中重复标记.您仍然可以根据需要手动布局模板，但这并不是绝对必要的.在Wicket中，标记需要反映在页面中创建的组件.Wicket中的想法是Java开发人员实际上并不创建或维护模板，而是由设计人员处理.

Another difference is that in Click controls knows how to render themselves, so you don't have to repeat the markup in your page templates. You can still manually layout your templates if you want, but it is not strictly necessary. In Wicket the markup needs to reflect the components created in the page. The idea in Wicket is that the Java developer doesn't actually create or maintain the templates, instead this is handled by a designer.

亲切的问候

鲍勃

这篇关于Apache Wicket与Apache Click的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！