Hi,
Sure, we must use async communications when running GWT application in
browser.
However, it is slow when testing our apps using GWTTestcase, and
normally we want to extends JUnit's Testcase instead.
Let see the ExampleJRETest in
http://code.google.com/webtoolkit/doc/latest/tutorial/mvp-architecture.html
public class ExampleJRETest extends TestCase {
// OLD: mockRpcService = createStrictMock
(ContactsServiceAsync.class);
// NEW
mockRpcService = SyncProxy.newProxyInstance
(ContactsServiceAsync.class, http://localhost/contactApp;,
contact);
...
}
And we can test our RPC service directly from JRE.
Hope this clarify.
On Jan 11, 3:01 am, Open eSignForms yoz...@gmail.com wrote:
Don't know anything about that library, but there's something odd about a
synchronous GWT RPC library that can simulate async when GWT RPC is async
to begin with, and very few would recommend using synchronous RPC in a
browser since it would appear to hang while the RPC took place.
We've found GWT RPC to be reliable and easy to program using the natural
async nature of javascript communications that browsers support.
--
You received this message because you are subscribed to the Google Groups
Google Web Toolkit group.
To post to this group, send email to google-web-tool...@googlegroups.com.
To unsubscribe from this group, send email to
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-web-toolkit?hl=en.
