Ok, the build output just looks like the standard linker was used. Since its still the nocahe.js and html files
The output error looked the same as before: Unsafe JavaScript attempt to access frame with URL http://localhost:8080/webclient/ from frame with URL http://cmdev:8888/pe/PE/DBFC82AC1D77661A91A0E32C1F2FA501.cache.html. Domains, protocols and ports must match. On Wed, Oct 19, 2011 at 5:17 PM, Thomas Broyer <[email protected]> wrote: > No, all linkers will generate a *.nocache.js (so changing linker doesn't > require changing the HTML host page) and all related files will be > linker-specific; in particular, xsiframe generates *.cache.js, while the > standard linker generates *.cache.html files. > > And about "doesn't work loaded from a different domain", what's your > browser saying? (in its error console) > > -- > You received this message because you are subscribed to the Google Groups > "Google Web Toolkit" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/google-web-toolkit/-/Bqs5gUWWHRgJ. > > 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. > -- 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.
