Cross domain builds

[Luis Montes]

I'm trying to get a cross domain build of my app, so I added:

<add-linker name="xs" />  to my module xml file

I'm getting:  [ERROR] Invalid linker name 'xs'

I found an example where I could define the linker as:

<define-linker name="xs" class="com.google.gwt.dev.linker.XSLinker" />

but that class doesn't seem to exist in GWT 2.3

Is there a different way to do a cross domain build now?

Luis

[Thomas Broyer]

I didn't remember the linker being removed, but it's been deprecated for some time now. It's been replaced by the xsiframe linker.

[Luis Montes]

I've added an xsiframe linker.  Should I have gotten an additional -xs.js file?  The standard looking js file it created doesn't work loaded from a different domain.

Luis

On Wed, Oct 19, 2011 at 12:00 PM, Thomas Broyer <t.br...@gmail.com> wrote:

I didn't remember the linker being removed, but it's been deprecated for some time now. It's been replaced by the xsiframe linker.

--
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/-/GKer7N469GgJ.
To post to this group, send email to google-we...@googlegroups.com.
To unsubscribe from this group, send email to google-web-tool...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.

[Thomas Broyer]

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)

[Luis Montes]

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 <t.br...@gmail.com> 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.