Re: Custom Post Linker and Super Dev Mode

[Geoffrey Wiseman]

On Tuesday, January 28, 2020 at 4:48:32 AM UTC-5, Thomas Broyer wrote:
>
> Those methods are to be called from the client code, not the linker itself.
>

Ok -- makes sense. If I modify the client code that makes those requests to 
use getModuleBaseForStaticFiles(), it looks like it's now trying to load 
them from the code server port instead -- assume that's expected?  If I log 
the output of both methods, I can see the ports are different.

Unfortunately, the new base URL doesn't seem to have helped me. Now I see 
"[WARN] ignored get request: /path/to/file" for the URL and if I make a 
curl request, I can see that it's coming back with a 200 and content length 
0.

So  it's different, but not totally working either?

-- 
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 google-web-toolkit+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/8f3c1799-877d-4779-b4f7-abbb1f5ca9a1%40googlegroups.com.

Re: Maven Plugin for GWT: "An internal error occurred during: "BBj - GWT Compile". Model not available for BBj"

['Jim Douglas' via GWT Users]

Still feeling my way around this. It seems clear that there was a bug 
introduced in Eclipse 2019-09 that still exists in Eclipse 2019-12. This 
Eclipse bug report shows the same basic error from a different context:

https://bugs.eclipse.org/bugs/show_bug.cgi?id=550966

The challenge here is that the package in question doesn't use Gradle at 
all.

On Monday, January 27, 2020 at 10:39:54 AM UTC-8, Jim Douglas wrote:
>
> Gradle is used in another package in this project, but not in the package 
> where I'm trying to do a GWT Compile; this package doesn't use gradle at 
> all.
>
> I do see reports of this same internal gradle exception in recent Eclipse 
> distributions:
>
> https://github.com/eclipse/buildship/issues/943
>
> https://github.com/microsoft/vscode-java-debug/issues/681
>
> On Saturday, January 25, 2020 at 9:51:32 AM UTC-8, Jens wrote:
>>
>> Looks like Eclipse wants to resolve classpath entries using Gradle 
>> (through Eclipse Buildship Plugin bundled with Eclipse to support project 
>> configuration based on Gradle).
>>
>> Maybe Gradle is enabled in your project for any reason, even though you 
>> are using Maven?
>>
>> -- J.
>>
>

-- 
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 google-web-toolkit+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/4bdf1ddb-01a7-43ee-834f-5ee2978046bd%40googlegroups.com.

Re: Custom Post Linker and Super Dev Mode

[Thomas Broyer]

On Monday, January 27, 2020 at 10:39:01 PM UTC+1, Geoffrey Wiseman wrote:
>
> 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.
>

Those methods are to be called from the client code, not the linker itself.
 

> But with this response I was able to find another thread:
>
> https://www.mail-archive.com/google-web-toolkit@googlegroups.com/msg105012.html
>
> 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?
>

If you emitString() with a partialPath of "foo.txt", then it should be 
accessible in SDM at GWT.getModuleBaseForStaticFiles() + "foo.txt" (but not 
GWT.getModuleBaseURL() + "foo.txt"). In production mode, it'll be 
accessible through both, as getModuleBaseForStaticFiles and 
getModuleBaseURL return the same value then.
 

-- 
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 google-web-toolkit+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/9fa84541-4581-4247-88ac-88b1cee60389%40googlegroups.com.