GWT 与 Apache Wicket [英] GWT vs Apache Wicket

问题描述

GWT 和 Wicket 都是有状态的，基于 Java 对象的.GWT 完全基于客户端，具有 javascript 优化、CSS 优化等功能，而且我对 Apache Wicket 还是很陌生.

Both GWT and Wicket are stateful, java object oriented based. GWT is completely client based with features like javascript optimization, CSS optimization, and I'm pretty new to Apache Wicket.

我对 Wicket 的了解越多，它与 GWT 的感觉就越相似.

The more I read about Wicket the more similar it feels to GWT.

所以我想问题是 - GWT 和 Wicket 之间有什么区别?还是我将苹果与橙子进行比较?

So I guess the question is - What are the differences between GWT and Wicket? Or am I comparing apples to oranges?

推荐答案

几乎是苹果对橘子.

这个维基条目总结了一些相同点和不同点，以及将它们一起使用的策略的开始，我认为这是一个有趣的想法.

This wiki entry summarizes some of the similarities and differences, and the start of a strategy for using them together, which I think is an interesting idea.

Wicket 主要是一种服务器端技术，具有一些内置的 Ajax 支持和用于连接更多 Ajax 的钩子.它不像 GWT 那样将 Java 转换为 JavaScript.它在服务器端维护状态，而 GWT 在客户端维护状态.

Wicket is primarily a server-side technology with some built-in Ajax support and hooks for wiring in more Ajax. It does not translate Java to JavaScript like GWT. It maintains state server-side where GWT maintains state on the client.

两者都是基于组件的，对我来说都有一种 Swing 开发的感觉(尽管 Wicket 似乎至少对其他受访者来说不像 Swing).

Both are component-based and to me have something of the feeling of Swing development (though Wicket doesn't seem to feel like Swing to at least one other respondent).

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