On Wednesday, January 15, 2020 at 3:49:34 AM UTC-5, Thomas Broyer wrote:--
IIRC, with Super Dev Mode, public artifacts aren't generated in the launcher dir; you need to build your path relative to GWT.
getModuleBaseForStaticFiles()rather than GWT.getModuleBase(). HTH
Cautionary preamble: I wasn't involved in the creation of this linker, and I haven't done much with GWT linkers, so it is entirely possible that I'm missing something here. Having said all that:
The linker that I've seen break down in SuperDevMode just calls `emitString` to create some text resources that are then requested later by the browser. Those resources were visible to dev mode in the past, and they're visible in the built GWT application, but in SuperDevMode, they 404. Near as I can tell, the linker isn't using `getModuleBase` or `getModuleBaseForStaticFiles` at all.
But with this response I was able to find another thread:
Sounds like you were saying there that it may not be possible to fix this for SuperDevMode? It definitely *does* work in the final built WAR file, it's only SuperDevMode where this seems to break down. So if I create artifacts using `emitString` in a custom linker, there's no way to have these be accessible in SuperDevMode?
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to firstname.lastname@example.org.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/c81f5a6e-b776-4b76-ba54-34e5e4a7f98b%40googlegroups.com.
Post a Comment