you can try to compile for xs, add <add-linker name="xs" /> to your
GWT Module xml

I had to do something even nastier, I was loading whole apps from
multiple machines into an IFrame and do app-to-app JavaScript
communication.

there are two solutions to this problem

1) explicit domain lowering, using www.a.mydomain.com and www.b.mydomain.com,
at the top of the page in JS, do  document.domain = "mydomain.com"

2) channel all requests through www.b.mydomain.com machine and use
Apache's Proxy features to do ProxyPass for some paths:

ProxyPass /gwtApp http://www.a.mydomain.com/gwtApp

Domain lowering will be hard to do if you are just loading your GWT js
tho.



On Jun 4, 12:53 am, JohnJ <[email protected]> wrote:
> What I am trying to do seems trivial but I must be missing
> something...
>
> I want to host the GWT application (CSS, JavaScript) on one domain:
>
>  http://www.server-a.com/gwtApp/
>
> and then have the html that hosts the application live on various
> other domains (sort like what adWords does):
>
>  http://www.server-b.com/hostpage.html
>
> I haven't gotten to the point where I'm doing RPC (I plan to use
> JSONP). The issue seems to be in the sniffer code for deferred binding
> -- like it's having trouble loading the right cache.js file.
>
> When I compile w/ PRETTY and look at the errors in Firebug i see the
> following...
>
> Permission denied to get property Window.prototypea
> [Break on this error] if ($wnd.prototypea) $wnd.prototypea.onScriptLoad
> ();
>
> I have seen references to a "mashup mode" in the forums but i have a
> feeling that's not around anymore.
>
> Please help.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to