On Nov 24, 5:37 pm, chewy <[email protected]> wrote:
> Hi,
>
> I have built my application in GWT and the resulting .js file, I want
> to inject to my web page.
> This works fine locally.
>
> But when I put the GWT .js file on my webserver and use <script
> type="text/javascript" language="javascript" src="http://
> mywebserver.com/myApp.nocache.js"></script> to call the .js file and
> inject to my web page - firefox gives me security errors.
>
> Now from reading the forums, there is a cross domain issue here - but
> in reality there is no issue as I built the same javascript app
> manually and located it on my webserver and called the .js file from
> another webpage on another server - the app worked with out any error.
> So why does the .js files produced by the GWT cause these security
> errors.
That's because GWT actually load your app in a hidden iframe; because
the iframe isn't in the same domain ("origin" actually) as your "host
page", they cannot communicate.
> anybody have a work around?
Let's rather call it a solution (*the* solution, at least the blessed
one): add the following in your module:
<add-linker name="xs" />
(unfortunately, the documentation isn't up-to-date and still
references the 1.4.x way of doing things)
--
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.
