具有gwt requestfactory的Smartgwt DataSource等

问题描述

有没有人有一个使用新的GWT结构为 RequestFactory 使用SmartGWT数据源用于数据绑定小部件的示例？

如果可能，我想创建一个通用数据服务，其中包含 listAll ， getByExample ， getByPrimaryKey 等我beleibe它应该有可能？

如果使用 RequestFactory ，将数据源放在一起并直接处理小部件字段是否有意义？

干杯，
Andy

解决方案

http://forums.smartclient.com/showthread.php?t=10850&highlight=GwtRPCDatasource

这个链接提供了一个带有RPC的smartgwt数据源的实现。我认为应该很容易将其扩展到RequestFactory。

关于抛弃DataSource，我会反对它。我用它创建了一个应用程序并相信我，smartgwt小部件与数据源非常根深蒂固。小部件的许多香草功能取决于数据源。为了将数据通道放在一起并尝试使用这些小部件变得非常复杂。我总是感觉到smartgwt在文档上的吝啬，这会给你带来很大的困扰。

因此，除非您对smartgwt的工作原理有一个非常好的理解，否则更喜欢数据源！

Does anyone have a working example of using the new GWT constructs for RequestFactory with a SmartGWT DataSource for databound widgets ?

If possible I would like to make a generic data service that contains methods for listAll, getByExample, getByPrimaryKey etc. I beleibe it should be possible ???

If using RequestFactory would it make sense to ditch the datasource altogether and work directly with the widget fields ?

Cheers,Andy

解决方案

http://forums.smartclient.com/showthread.php?t=10850&highlight=GwtRPCDatasource

This link provides an implementation of smartgwt datasource with RPC. My take is it should be easy to extend it to RequestFactory.

About ditching DataSource, I would advice against it. I have created an application with it and trust me, smartgwt widgets are very deeply ingrained with a datasource. A lot of vanilla functionality of the widgets depends on datasource. To ditch the datasouce all together and try and use the widgets gets pretty complicated. I always have felt that smartgwt skimps on documentation, and that will hit you hard.

So prefer a datasource unless you have a very gooood understanding of how smartgwt works!

这篇关于具有gwt requestfactory的Smartgwt DataSource等的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！