I asked the same question a while back:
http://groups.google.com/group/Google-Web-Toolkit/browse_thread/thread/3c06837fb6bfe732/5acff8e39b098cc2
I'll offer the same advice that I was given - search these forums for
info on "Same Origin Policy" (SOP). This is a restriction that
basically means you can only make RPC calls to the server that served
the page containing the GWT control rather than the server that served
the actual GWT html file assets. There's plenty of good information
in these groups on that subject.
What I had more difficulty in finding out however was that you'll also
need to add the following entry to your GWT project's XML config
(below your <inherits> entries):
<!-- Enable cross site location of GWT compiled assets. Required for
LIVE deployment only. Will not work in hosted mode. -->
<add-linker name="xs" />
As the comment suggests, this config will *not* work in hosted mode,
so you'll need to have different config files for development and
production environments.
>From personal experience, I moved the deployment all my static assets,
inc. GWT html files, to Amazon's CloudFront and saw an absolutely
amazing improvement in the perceived performance of my application.
Good luck,
Chris.
On Mar 30, 7:59 am, Ghostcoder <[email protected]> wrote:
> I have seen some post on runasync feature in GWT ,I like to test that
> feature can someone suggest the correct stable revision which i can
> use to test this feature.
>
> Do we need JAVA SDK 1.6 to build the source code in the trunk?
>
> Thankyou
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/Google-Web-Toolkit?hl=en
-~----------~----~----~----~------~----~------~--~---
