将Google Web Toolkit(GWT)用作成熟的Java Web框架有意义吗? [英] Does it make sense to use Google Web Toolkit (GWT) as a full-blown Java web framework?
问题描述
我对GWT可能成为我整个表示层的基础的可能性感兴趣。
I am interested in the possibility that GWT could serve as the basis for my entire presentation layer.
我想知道是否有人尝试过这种方法 - 或者说失败 - 并且可以说服我或者不让我试图这样做。
I would be interested to know if anyone has tried this successfully - or unsuccessfully - and could persuade or unpersuade me from attempting this.
推荐答案
大约一年前,我和GWT一起工作过。当时,它似乎是一个好主意,有一些注意事项:
I worked with GWT about a year ago. At the time it seemed like a great idea, with a number of caveats:
- 我对API的某些部分有疑难杂症问题,这可能与你编码的事实有关,因为你实际上是在编写一个单独编译的Java环境编译环境,所以你做了一些不正确的假设(在这种情况下,传递嵌套值到前端)。我认为还有另一个重写我的ant脚本使用32位jvm进行gwt编译。
- 我花了一些时间试图调整外观 - 我们从未部署完成项目,所以我不确定这会花费多少工作才能达到专业级别,但它似乎(在逻辑上)像调整一个swing界面。可能比html更直观,直观。
- 因为ajax在最终产品中对你来说是如此隐藏,所以如果性能差,我可能会做些什么。
这就是说,它绝对值得玩,我的经历很久以前在互联网时代,特别是给予现在它可能更成熟了。另外值得指出的是,这是一种从大多数MVC框架开发GUI代码的非常不同(并且令人耳目一新)的方式,值得一看,除此之外没有其他原因。
That being said,it definitely seems worth playing with, and my experiences were a long, long time ago in internet years, especially given that it's probably much more mature now. It's also worth pointing out that it's a very different (and refreshing) way of developing GUI code from most MVC frameworks, and worth a look if for no other reason than that.
我的感觉是,如果你正在构建一个高负载的专业网站,要求非常苛刻的图形要求,GWT可能不是一个好的选择,否则就是好的。
My feeling is that if you're building a high-load professional site with very demanding graphical requirements GWT is probably not a good choice, otherwise ok.
这篇关于将Google Web Toolkit(GWT)用作成熟的Java Web框架有意义吗?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!