我们计划使用智能GWT，GWT和相关框架为客户端丰富的接口和Spring MVC返回在服务器端JSON数据。

We plan to use smart GWT, GWT and related frameworks for the client side rich interface and Spring MVC which returns JSON data on the server side.

作为调查的一部分，看它是否符合我们的要求，以下问题需要一些答案：

As part of the investigation to see if it fits our requirement, the following questions need some answers :

SmartGWT的都有自己的做法是，如果你使用一个小部件，引入一个数据源到它和你做。尚未发现有关在模块化的（或MVP）的方式建立这种智能GWT组件的最佳实践。任何建议

SmartGWT has its own approach, where you use a widget, introduce a datasource into it and you are done. Yet to identify the best practise around building such smart GWT components in a modularised (or MVP) fashion. Any suggestions

使用框架GWT平台和SmartGWT的可能是一种选择，尝试MVP架构这里提到。有什么建议？

Using framework GWT-platform and SmartGWT could be an option to try MVP architecture as mentioned here. Any suggestions?

验证/消息/异常显示等通用功能支持智能GWT是待调查。

Validation/message/exceptions display and other generic feature support of smart GWT is yet to be investigated.

客户端服务器架构：有在服务器端和GWT +智能GWT在客户端的Spring MVC +弹簧核心可能是开源技术的一个很好的堆栈，但鉴于GWT在默认情况下使用RPC客户端服务器相互作用，这些需要使用，以得到更好的评估。 （特别是认证/会话处理/安全等）。有什么建议？

Client server architecture: Having Spring MVC + Spring core on the server side and GWT + Smart GWT on the client side could be a good stack of open source technologies, but given that GWT by default uses RPC for client server interaction, usage of these needs to be better evaluated. (esp. authentication/session handling/security etc). Any suggestions?

感谢

推荐答案

我神经使用的SmartGWT或任何其他丰富的图书馆。我的观点可能有失偏颇，但我真的认为GWT组件容易定制和轻量化。这件事情我从来不觉得从SmartGWT的到来是该类型的任何其他LIBRAIRIE。

I nerver used SmartGWT or any other rich libraries. My opinions may be biased, but I really think that Gwt components are easy to customize and lightweight. That's something I never felt coming from SmartGwt are any other librairie of that type.

话虽这么说，这是我回答你的两个关注的：

That being said, here's my answer to two of your concern:

使用框架GWT平台和SmartGWT的可能是一种选择，尝试MVP架构这里提到。有什么建议？

Using framework GWT-platform and SmartGWT could be an option to try MVP architecture as mentioned here. Any suggestions?

好了，留MVP就像在这方面，只要设置从presenter数据源。在您看来，SmartGWT的部件应该是被动，并等待来自presenter配置来了。

Well, to stay MVP like in that aspect, just set the datasource from the presenter. In your view, the SmartGWT widget should be "passive" and wait for configuration coming from the presenter.

优点：你不必进行单元测试的看法，因为SmartGWT的部件应该已经被很好的测试。你只需要测试presenter，你实际上调用视图以配置窗口小部件和设备是否正确地调用它。

Advantage: You don't have to unit test the view, since SmartGWT widgets should already be well tested. You only have to test the presenter where you actually call the view to configure that widget and verify if you call it correctly.

客户端服务器架构：有在服务器端和GWT +智能GWT在客户端的Spring MVC +弹簧核心可能是开源技术的一个很好的堆栈，但鉴于GWT在默认情况下使用RPC客户端服务器交互，使用这些需要被更好评估。 （特别是认证/会话处理/安全等）。有什么建议？

Client server architecture: Having Spring MVC + Spring core on the server side and GWT + Smart GWT on the client side could be a good stack of open source technologies, but given that GWT by default uses RPC for client server interaction, usage of these needs to be better evaluated. (esp. authentication/session handling/security etc). Any suggestions?

RPC是一个选项，而不是默认的通信。还有其他两个类型的通信（甚至更多，如果你尝试实验性的功能就像DeRPC）：RequestBuilder和RequestFactory

RPC is an option, not the default communication. There's two other type of communication (and even more if you try experimental feature like DeRPC): RequestBuilder and RequestFactory.

RequestBuilder可能会使用到HTTP GET与JSON响应。不能帮你的智能GWT方法。

RequestBuilder could be use to HTTP GET with JSON Response. Can't help you for the smart GWT approach.

下面是GWT平台的用户使用智能GWT，阅读他的博客，它应该启发你： http://uptick.com.au/blog

Here's a user of Gwt-Platform that use Smart GWT, read his blog, it should enlighten you: http://uptick.com.au/blog

在写这个答案的时候，博客下跌，但应该很快回来。

At the time of writing this answer, the blog was down, but it should come back soon.