Calling *.nocache.js from a remote page

27 views
Skip to first unread message

Alexander Orlov

unread,
Sep 10, 2011, 9:20:53 AM9/10/11
to google-we...@googlegroups.com
Usually 

<script src="module.nocache.js"></script>

is what you put into your container page. But what if I want to call the module from a remote page?


...doesn't work. Or is it necessary for *.nocache.js to be in the same folder where the container.html is? Using an iframe could solve the problem but I don't want to use iframes for promotional reason. Everybody who looks at the source code should be immediately able to see the GWT source reference without calling the iframe source.

Thomas Broyer

unread,
Sep 10, 2011, 10:15:47 AM9/10/11
to google-we...@googlegroups.com
See http://code.google.com/webtoolkit/doc/latest/FAQ_Server.html#What_is_the_Same_Origin_Policy,_and_how_does_it_affect_GWT?

Except: use the newer "xsiframe" linker instead of oldish and soon to be deprecated "xs" one.

Alexander Orlov

unread,
Sep 10, 2011, 9:29:22 PM9/10/11
to google-we...@googlegroups.com
Thx, worked like a charm!
Reply all
Reply to author
Forward
0 new messages