GWT VS阿帕奇检票 [英] GWT vs Apache Wicket

问题描述

GWT和Wicket的是有状态的，Java对象面向基础。 GWT是完全基于像优化的JavaScript，CSS优化功能的客户端，我pretty新到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.

我读到检票感觉来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?

推荐答案

有pretty多拿苹果和橘子。

It is pretty much 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.

检票主要是一个服务器端的技术，一些内置的Ajax支持和更多的Ajax布线挂钩。它不是Java转换为JavaScript的GWT一样。它保持状态的服务器端，其中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开发的感觉的东西（虽然检票似乎并不觉得自己的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 VS阿帕奇检票的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！