Re: Superdevmode and ReferenceErrors

That made my day! I was encountering those issues a lot when using Lambda expressions - and renaming a Lambda is rather difficult... Thanks! On Wednesday, February 24, 2021 at 10:36:38 PM UTC+1 David Nouls wrote: > I just browse to the sdm website at http://localhost:9876 and click on de >

Re: Superdevmode and ReferenceErrors

Hi, On Thu, Feb 25, 2021 at 6:51 AM Stik wrote: > Occasionally when running under SDM in Eclipse I will get a > "ReferenceError: _g$ is not defined" from the browser. The usual > "fix" is to rename the symbol in question, reload, and the issue is gone. > If i then rename it back to what it

Re: Superdevmode and ReferenceErrors

Huh, did not know that was there - thanks! Stik On Wednesday, February 24, 2021 at 9:36:38 PM UTC David Nouls wrote: > I just browse to the sdm website at http://localhost:9876 and click on de > button to clear the cache > On 24 Feb 2021, 22:20 +0100, Stik , wrote: > > Aha, how do you clear

Re: Superdevmode and ReferenceErrors

I just browse to the sdm website at http://localhost:9876 and click on de button to clear the cache On 24 Feb 2021, 22:20 +0100, Stik , wrote: > Aha, how do you clear the cache? i've never been sure where SDM is hiding it > Stik > > > On Wednesday, February 24, 2021 at 8:40:05 PM UTC David Nouls

Re: Superdevmode and ReferenceErrors

Aha, how do you clear the cache? i've never been sure where SDM is hiding it Stik On Wednesday, February 24, 2021 at 8:40:05 PM UTC David Nouls wrote: > It is a known issue with incremental compilation. It is annoying but I > tend to just clear the sdm cache and reload. > On 24 Feb 2021, 20:50

Re: Superdevmode and ReferenceErrors

It is a known issue with incremental compilation. It is annoying but I tend to just clear the sdm cache and reload. On 24 Feb 2021, 20:50 +0100, Stik , wrote: > Occasionally when running under SDM in Eclipse I will get a "ReferenceError: > _g$ is not defined" from the browser.   The usual "fix"

Superdevmode and ReferenceErrors

Occasionally when running under SDM in Eclipse I will get a "ReferenceError: _g$ is not defined" from the browser. The usual "fix" is to rename the symbol in question, reload, and the issue is gone. If i then rename it back to what it used to be called, so nothing has actually changed, it

Re: Unknown argument: -superDevMode

Thanks. I just switched back to 2.7 On Mon, Sep 14, 2020, 1:35 AM Thomas Broyer wrote: > If you want to use SuperDevMode in GWT 2.5 or 2.6, then you have to use > the CodeServer entrypoint (rather than DevMode). > I don't know if the Eclipse plugin has built-in support for it; you mig

Re: Unknown argument: -superDevMode

If you want to use SuperDevMode in GWT 2.5 or 2.6, then you have to use the CodeServer entrypoint (rather than DevMode). I don't know if the Eclipse plugin has built-in support for it; you might have to create a launch configuration from scratch. (why would you want to use such an old GWT

Re: Unknown argument: -superDevMode

Here are the arguments from Run Congiurations: -superDevMode -remoteUI "${gwt_remote_ui_server_port}:${unique_id}" -startupUrl ChordEarTrainer.html -logLevel INFO -codeServerPort 9997 -port -war C:\Users\James-PC\workspace\FINALWORKINGSPACE1\ChordEarT

Unknown argument: -superDevMode

the option from right click to synchornize sdk or something like that. Here is the full error. Unknown argument: -superDevMode Google Web Toolkit 2.6.1 DevMode [-[no]startServer] [-port port-number | "auto"] [-whitelist whitelist-string] [-blacklist blacklist-string] [-logdir

Re: Question about SuperDevMode/codeserver

It would indeed work (most of the time I believe), but then you need to make sure to force the GWT compiler to compile your code before deploying, because it's really easy to get false positives in the staleness check (if the superdevmode stub *.nocache.js modification time is more recent than

Re: Question about SuperDevMode/codeserver

I added in a local maven profile an extra property file to instruct sprint boot where check the static resources. spring.resources.static-locations=${gwtBasePathLocation},classpath:/META-INF/resources/,classpath:/resources/,classpath:/static/,classpath:/public/ On Wed, 6 Mar 2019 at 11:13 Bryan

Re: Question about SuperDevMode/codeserver

I was able to set the launcherDir to server/target/classes/static and that seems to make it work the way I was expecting. On Tuesday, 5 March 2019 13:55:54 UTC-5, Bryan Bende wrote: > > Hello, > > I have a multi-module Maven project setup similar to the multi-module > archetype, but created

Question about SuperDevMode/codeserver

Hello, I have a multi-module Maven project setup similar to the multi-module archetype, but created before I knew about that, using GWT 2.8.2 and the gwt-maven-plugin 1.0-rc-9. shared - Contains DTOs with JS interop annotations, packaged as gwt-lib client - GWT code, depends on shared as

Having a serious issue with superdevmode and /tmp/gwt-* corruption?

I have a gradle/eclipse project that when I remove /tmp/gwt-*, do a gradle clean build farmrun, then do a gradle gwts, everything works as expected, and I can make "one set of changes", run sdm=>recompile link, everything still works, make "a second set of changes", run sdm=>recompile link,

Re: Problems Remote Debugging with SourceMaps in SuperDevMode

You could try https://github.com/tbroyer/gwt-devserver On Tuesday, June 12, 2018 at 10:26:13 AM UTC+2, Carlo wrote: > > Hello, > > sorry for resuming this old thread. > I have as well a code server running on remote and I would like to use SDM > via my local browser. SDM works fine but it seems

Re: Problems Remote Debugging with SourceMaps in SuperDevMode

Hello, sorry for resuming this old thread. I have as well a code server running on remote and I would like to use SDM via my local browser. SDM works fine but it seems that the browser never asks for the source maps. I see in the sdm logs "source maps enabled", but then I cannot see any

Re: SuperDevMode OutOfMemoryError

e have a large project with about 250 KLoC client-side code (without > comment and blank lines). This project compiles in DevMode with Xmx2500m in > 3mins. But in SuperDevMode it throws OutOfMemoryError. > > *GWT Libraries:* GWT 2.8.2, gwittir, gwtchosen, gwtquery > > *DevMode:* >

SuperDevMode OutOfMemoryError

Hi, We have a large project with about 250 KLoC client-side code (without comment and blank lines). This project compiles in DevMode with Xmx2500m in 3mins. But in SuperDevMode it throws OutOfMemoryError. *GWT Libraries:* GWT 2.8.2, gwittir, gwtchosen, gwtquery *DevMode:* *Compiler Arguments

Re: SuperDevMode recompiles RPC since they are unchanged

Hi again, I wonder my issue is related with https://github.com/gwtproject/gwt/issues/7519 19 Eylül 2017 Salı 17:05:34 UTC+3 tarihinde Hakan Cunier yazdı: > > Hi, > We are using GWT 2.7.0, and trying SuperDevMode. Works well unless you > restart the jetty server. After st

Re: SuperDevMode recompiles RPC since they are unchanged

On Wednesday, September 20, 2017 at 11:25:45 AM UTC+2, Ignacio Baca Moreno-Torres wrote: > > Eh! the bookmark (or similar tool > https://gist.github.com/ibaca/1dc87a58ee542840a5f90c5ff2931329) are still > useful if you use only the codeserver. > If you mean "only the codeserver", without an

Re: SuperDevMode recompiles RPC since they are unchanged

Eh! the bookmark (or similar tool https://gist.github.com/ibaca/1dc87a58ee542840a5f90c5ff2931329) are still useful if you use only the codeserver. On mié., 20 sept. 2017 10:51 Jens wrote: > > Hey Jens, nobody should use the bookmarklets in 2.7 either ;-) >> > > Oh

Re: SuperDevMode recompiles RPC since they are unchanged

> Hey Jens, nobody should use the bookmarklets in 2.7 either ;-) > Oh indeed, mmmh I guess mixing it up was a symptom of always using some custom build of GWT :-) -- J. -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this

Re: SuperDevMode recompiles RPC since they are unchanged

On Tuesday, September 19, 2017 at 5:30:11 PM UTC+2, Jens wrote: > > IMHO it is preferable to launch SuperDevMode and your server (be it jetty > or anything else) separately so you can restart them separately. We do that > at work and only rarely restart SuperDevMode. > I whole

Re: SuperDevMode recompiles RPC since they are unchanged

IMHO it is preferable to launch SuperDevMode and your server (be it jetty or anything else) separately so you can restart them separately. We do that at work and only rarely restart SuperDevMode. Generally restarting SuperDevMode in GWT 2.8.x works better as GWT 2.8.x stores a cache on disk

SuperDevMode recompiles RPC since they are unchanged

Hi, We are using GWT 2.7.0, and trying SuperDevMode. Works well unless you restart the jetty server. After starting jetty in superdevmode and launch chrome (sdbg) it compiles and generates rpc manifests. Well no problem, when you shutdown and start jetty, same compilation/calculation thing

How to determine whether you're in SuperDevMode inside (custom) linker code

You can look for the "superdevmode" property value out of the LinkerContext. The tricks you mention are for client-side code, at runtime; not at compile-time. As for GWT.create(), have a look at ServerGWTBridge to see how that could be used outside of GWT client code. Though I'd

How to determine whether you're in SuperDevMode inside (custom) linker code

a runtime exception saying I can only use in "client code" (which I guess excludes the linker). So the trick involving the superdevmode property and deferred binding also doesn't work. So how can I detected SDM inside the linker? -- You received this message because you are

Re: GWT 2.7 SuperDevMode Compile Times

;) On Monday, April 3, 2017 at 10:31:24 PM UTC+8, Thomas Broyer wrote: > > > > On Monday, April 3, 2017 at 1:56:28 PM UTC+2, Thomas wrote: >> >> @tbroyer, sorry, yes, they are strings. Will check out the archetype(s) >> and see how we can handle shared enums easiest. Splitting it up might give

Re: GWT 2.7 SuperDevMode Compile Times

On Monday, April 3, 2017 at 1:56:28 PM UTC+2, Thomas wrote: > > @tbroyer, sorry, yes, they are strings. Will check out the archetype(s) > and see how we can handle shared enums easiest. Splitting it up might give > me some other advantages as well. > How certain are you about compile times? >

Re: GWT 2.7 SuperDevMode Compile Times

@DavidN - Wow, how can anyone work productively with 30+ mins ??? On Monday, April 3, 2017 at 7:48:15 PM UTC+8, DavidN wrote: > > You are complaining of a startup of 1 minute ? I know some projects that > have 30+ minutes with GWT 2.7! In those cases there are a lot of reasons > why their

Re: GWT 2.7 SuperDevMode Compile Times

@tbroyer, sorry, yes, they are strings. Will check out the archetype(s) and see how we can handle shared enums easiest. Splitting it up might give me some other advantages as well. How certain are you about compile times? On Monday, April 3, 2017 at 7:01:57 PM UTC+8, Thomas Broyer wrote: > > >

Re: GWT 2.7 SuperDevMode Compile Times

t; > -Dgwt.speedtracerlog=/tmp/speedtracer.gwt.json > -Dgwt.speedtracerformat=RAW > > as JVM parameter of SuperDevMode but you would need some way to visualize > it (unless you are fine reading raw data). > > > -- J. > -- You received this message because you are subscribed to

Re: GWT 2.7 SuperDevMode Compile Times

You are complaining of a startup of 1 minute ? I know some projects that have 30+ minutes with GWT 2.7! In those cases there are a lot of reasons why their compile time is so long. In my current app I also have about 2 minutes startup time and an incremental reload of about 5 seconds. We are also

Re: GWT 2.7 SuperDevMode Compile Times

On Monday, April 3, 2017 at 10:49:00 AM UTC+2, Thomas Buckel wrote: > > Also wondering how to split client and server into different mvn modules > when using ReqFactory - @ProxyForName and @ServiceName should work for > class names, however they still require a class reference to the >

Re: GWT 2.7 SuperDevMode Compile Times

as JVM parameter of SuperDevMode but you would need some way to visualize it (unless you are fine reading raw data). -- 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

Re: GWT 2.7 SuperDevMode Compile Times

Interesting. We're also using GIN and UiBinder, but also GWT-RequestFactory with editors/drivers. So lots to things to be generated. Also wondering how to split client and server into different mvn modules when using ReqFactory - @ProxyForName and @ServiceName should work for class names,

Re: GWT 2.7 SuperDevMode Compile Times

> Things I would try: > >- GWT 2.8; SDM will likely be faster >- removing server-side dependencies from GWT classpath; which means >with Maven splitting client and server code into separate modules. > > I guess it won't really help. We are in the same situation using some custom

Re: GWT 2.7 SuperDevMode Compile Times

On Monday, April 3, 2017 at 10:09:06 AM UTC+2, Thomas Buckel wrote: > > Hi all, > > I've been working on an enterprise GWT app for the last few years. It has > grown and will grow quite a bit and compile times (DevMode, SuperDevMode) > are becoming a real pain point

GWT 2.7 SuperDevMode Compile Times

Hi all, I've been working on an enterprise GWT app for the last few years. It has grown and will grow quite a bit and compile times (DevMode, SuperDevMode) are becoming a real pain point for the developers. A SuperDevMode initial compile takes about 50sec with GWT2.7/Java7 on a 2.6GHz i7

Re: GWT 2.7: access public static final field in JSNI results as undefined in SuperDevMode

thingWithMarker() { > nativeDoSomethingWithMarker(SPECIAL_MARKER); > } > private static native void nativeDoSomethingWithMarker(String cm) /*-{ > $wnd.alert(cm); > }-*/; > > In legacy devmode, JSNI boundaries used to be a performance issue, but > this is no longer the case

Re: GWT 2.7: access public static final field in JSNI results as undefined in SuperDevMode

nativeDoSomethingWithMarker(String cm) /*-{ $wnd.alert(cm); }-*/; In legacy devmode, JSNI boundaries used to be a performance issue, but this is no longer the case with SuperDevMode, so there's no reason to write big JSNI methods (or even JSNI at all: use JsInterop; there are still a few cases that need

GWT 2.7: access public static final field in JSNI results as undefined in SuperDevMode

e compiled version this is working. In SuperDevMode cm is undefined. Now, I remove the final and voila, it even works in SuperDevMode. So obviously the final is a problem. But why is it working in classic and compiled mode? Is this simply a bug or is there a better way to use such constant

[gwt-contrib] SuperDevMode slow compilation with stack trace emulation enabled

Hi, We're trying to compile a very large GWT project that generates in non obfuscated mode(PRETTY setting) around 41MB of nocache.js per module. It works fine but when enabling stack trace emulation(to have deobfuscated exception stack traces in Eclipse through SDBG), compilation gets stuck at

Re: SuperDevMode automatic recompile does not work with external server

Ah! - there is another gwt plugin :) Good to know! My missing link was that I did not know that SuperDevMode creates a special nocache.js file. Once I knew that it was simple to fix. I'll try your plugin asap... Thanks! Raphael On Fri, Apr 22, 2016 at 5:56 PM, Thomas Broyer <t.bro...@gmail.

Re: SuperDevMode automatic recompile does not work with external server

: > > That did the trick. Now it's working... Thanks Jens! I did not know > that there is a special SuperDevMode nocache.js file needed. > > Now things are a bit clearer. We used > ../ninja/src/main/java/assets/gwt > (aka gwt.war parameter) so that gwt compiled its js sources into

Re: SuperDevMode automatic recompile does not work with external server

Hmm. I just tried some options of the maven plugin but that did not work. But it's not important anyway. I integrated build step into our java server that copies over the nocache.js files of the gwt project into its assets folder. That works for both the superdevmode and the regular ones (when

Re: SuperDevMode automatic recompile does not work with external server

> SuperDevMode does not seem to respect gwt.war when compiling its > superdevmode.nocache.js. And that is the problem. The special > superdevmode.nocache.js gets created in the target folder of the > original gwt project. Our Java server knows nothing about it... > &g

Re: SuperDevMode automatic recompile does not work with external server

That did the trick. Now it's working... Thanks Jens! I did not know that there is a special SuperDevMode nocache.js file needed. Now things are a bit clearer. We used ../ninja/src/main/java/assets/gwt (aka gwt.war parameter) so that gwt compiled its js sources into the assets folder of our server

Re: SuperDevMode automatic recompile does not work with external server

First start SDM, then deploy your war to your external server. SDM generates a special *.nocache.js file that enables automatic recompilation. You have to make sure that this special version is deployed. -- J. -- You received this message because you are subscribed to the Google Groups "GWT

SuperDevMode automatic recompile does not work with external server

Hi, I just ran into an interesting problem while upgrading a very old GWT app to GWT 2.8.0-beta1 and its SuperDevMode (using the codehaus maven plugin). Our setup is basically that we got two projects: A GWT project, and a Java Server that acts as restful json backend. If I compile stuff via

Re: Missing class names in superdevmode

I haven't found the responsible "namer-code" by myself yet, I'll guess I have to live with the current display-scheme. If it's related to Chrome I'll be happy to investigate in that direction. Sadly I currently have no pointer which would lead me to this assumption. -- You received this

Re: GWT-2.8.0-SNAPSHOT SuperDevMode in Jetbrains IDEA - Exception in GWT ResourceAccumulatorManager after saving file

First THX Jens and Thomas, I would expect that the CodeServer should handle this correctly, so I will open an bug for the GWT project. Or is that a IDEA bug because the file is not hidden? Maybe you have also an idea why the first start of the CodeServer takes so long? BR Rocco Am

Re: GWT-2.8.0-SNAPSHOT SuperDevMode in Jetbrains IDEA - Exception in GWT ResourceAccumulatorManager after saving file

*___jb_old___ files are temporary files created by IntelliJ when safe write is enabled (Settings -> Appearance & Behavior -> System Settings -> Use "safe write"). Looks like the file has been deleted by IntelliJ between the time GWT has detected it was created (using Java watch service) and

Re: Missing class names in superdevmode

Do you know which class is responsible for naming the translated JavaScript-classes? All I could find right now were the namer for fields and methodnames. I guess that this is the part one would have to look into in order to understand, why the class names are shown as they do. -- You

Re: SuperDevMode

scribing how to debug GWT SuperDevMode in > Firefox? > SDBG only talks the Chrome Remote Debugging protocol, so it can't directly connect to Firefox. It might be possible to use https://github.com/RemoteDebug/remotedebug-firefox-adapter though (no idea how you use it, all I know is that it

Re: Missing class names in superdevmode

Yeah I tried to modify that parameter within the CodeServer. Sadly I wasn't able to get it to work. >From the mentioned commit all I found was that it only affects the naming of the field (JSIncrementalNamer on/off). But I couldn't find any evidence of the "class name" that is shown right to

Re: SuperDevMode

Whoops, I did have one more specific question. I followed Brandon's video to debug with Chrome, and it worked great: https://www.youtube.com/watch?v=icJEa5lcJaQ Is there a video, or notes, describing how to debug GWT SuperDevMode in Firefox? On Tuesday, March 29, 2016 at 11:35:01 AM UTC-7

Re: SuperDevMode

Thanks again for the pointers, Thomas. There's probably a cleaner approach, but I was able to get SuperDevMode to load by editing the SuperDevMode web app classpath to force gwt-dev.jar to the front of the list, to hide the jetty-all-9.2.10.jar from my default classpath. Debugging

Re: Missing class names in superdevmode

Hm I see. You probably have done DevMode -style, right? However in GWT 2.8 that DevMode class launches a different class called CodeServer which you can also start yourself. This CodeServer class has a -style parameter that you can use to modify the output. The corresponding commit to make that

Re: Missing class names in superdevmode

"-style" gives an error and even changing the JSOutputOption to PRETTY within a debugging session of CodeServer doesn't change the style. I would prefer an opt-out for this behaviour for maybe "not so big"-Projects. But it may have some deeper technical reasons that I don't see. Yes, maybe

Re: Missing class names in superdevmode

he primary reason this has been done is to reduce the amount of unoptimized JavaScript generated by SuperDevMode so that browsers can better handle it for large apps. Don't know from the top of my head if you can change that default by simply passing your own -style parameter. Never tried it.

Re: Missing class names in superdevmode

Does nobody have this problem? Or am I the only one, who's interested in the actual class being used (especially in polymorphism cases). I would like to maximize my productivity in a newly started project. Best regards Klemens Am Freitag, 18. März 2016 07:33:12 UTC+1 schrieb Klemens Schrage: >

Re: SuperDevMode

On Monday, March 21, 2016 at 11:21:21 PM UTC+1, Jim Douglas wrote: > > Hmm, that sounded like there might be a hint in there somewhere. :-) > > > You could also create a launch configuration for the SuperDevMode code > server directly because DevMode -noserver is th

Re: SuperDevMode

Hmm, that sounded like there might be a hint in there somewhere. :-) > You could also create a launch configuration for the SuperDevMode code server directly because DevMode -noserver is the same as starting the main class CodeServer. What does that mean in Eclipse, Jens? This is what I h

Re: SuperDevMode

With old/classic DevMode -noserver there is no jetty started at all so it did not matter if you have a jetty-all-9.2.10.jar on classpath or not. However with GWT 2.8 when executing DevMode -noserver the SuperDevMode CodeServer will be started which uses its own embedded jetty server/library

Re: SuperDevMode

ropped dead, I've just written it off and worked directly >>>> in JavaScript, adding debug logging as necessary to isolate problems. >>>> It's >>>> not optimal, but it's workable. I'm looking at SuperDevMode with GWT 2.8 >>>> now, and I'm strugg

Re: SuperDevMode

? >> >> On Mon, 21 Mar 2016 at 15:19 Jim Douglas <jdo...@basis.com> wrote: >> > Since DevMode dropped dead, I've just written it off and worked directly >>> in JavaScript, adding debug logging as necessary to isolate problems. It's >>> not optimal, but i

Re: SuperDevMode

ked directly >> in JavaScript, adding debug logging as necessary to isolate problems. It's >> not optimal, but it's workable. I'm looking at SuperDevMode with GWT 2.8 >> now, and I'm struggling. The documentation ( >> http://www.gwtproject.org/articles/superdevm

Re: SuperDevMode

workable. I'm looking at SuperDevMode with GWT 2.8 > now, and I'm struggling. The documentation ( > http://www.gwtproject.org/articles/superdevmode.html) suggests (possibly > overly optimistically?) that it just works; is that theoretically true, or > is it omitting crucial details? &g

SuperDevMode

Since DevMode dropped dead, I've just written it off and worked directly in JavaScript, adding debug logging as necessary to isolate problems. It's not optimal, but it's workable. I'm looking at SuperDevMode with GWT 2.8 now, and I'm struggling. The documentation (http://www.gwtproject.org

Missing class names in superdevmode

Hello, maybe I missed something within all those GWT 2.8 discussions / jsinterop announcements, but since switching to 2.8 beta (and even current snapshot) chrome doesn't show the variable's class name / type while debugging in dev tools. There is only the obfuscated name. Not the biggest deal

Re: SuperDevMode & java long value in debugger

ikov wrote: > > There is no such type long in JavaScript. > > On Thursday, February 4, 2016 at 10:56:05 AM UTC+3, Jack Thompson wrote: >> >> Hello, >> >> In SuperDevMode browser JS debugger console shows long values as JS >> object having properties l,h and m. >

Re: SuperDevMode & java long value in debugger

There is no such type long in JavaScript. On Thursday, February 4, 2016 at 10:56:05 AM UTC+3, Jack Thompson wrote: > > Hello, > > In SuperDevMode browser JS debugger console shows long values as JS object > having properties l,h and m. > > Is there any convenient way t

SuperDevMode & java long value in debugger

Hello, In SuperDevMode browser JS debugger console shows long values as JS object having properties l,h and m. Is there any convenient way to get the actual long value instead of having to use GWT.log in the actual java source? -- You received this message because you are subscribed

gwt 2.7.0 - superdevmode serialization is different than compiled serialization

Hi folks, Do you know why guava multimap could be serialized with superdevmode? I found a problem with a gwt compiled application but it didin't happen with superdevmode. I serialized a multimap using gwt-rpc and it worked for superdevmode, but no using the compiled application. Any thought

Re: SuperDevMode does not see sources from another project (Eclipse)

without rebuilding library's jar every time. This > works for regular Java code, but when I try to invoke SuperDevMode for a > module that uses some stuff from library, SDM complains that it can not > find sources for used classes. In Eclipse I have no problems > compiling AppPr

SuperDevMode does not see sources from another project (Eclipse)

flawlessly. However, while maintaining a library (e.g. adding feature that application uses), I find it useful to add LibProj on AppProj's build path and then hack on both sources without rebuilding library's jar every time. This works for regular Java code, but when I try to invoke SuperDevMode

Re: IntelliJ 15, SuperDevMode, AppEngine, Gradle

Hey Jens, Thanks for all the advice. I think I'm getting close, but I'm still not quite there yet. I added -noserver and -war path/to/my/exploded/war to my dev options for the SDM configuration. Now, I start SDM, then I start AppEngine and I've got: http://localhost:8080 (AppEngine server,

Re: IntelliJ 15, SuperDevMode, AppEngine, Gradle

Fellas, After further research, I discovered a very tricky and hard to detect bug: I forgot the damn entry point in my .gwt.xml Otherwise, everything is working really well. Thanks for all your help Jens! As a related question, Is there any way to debug SDM and AppEngine server at the same

Re: IntelliJ 15, SuperDevMode, AppEngine, Gradle

> After further research, I discovered a very tricky and hard to detect bug: > I forgot the damn entry point in my .gwt.xml > ouch..glad you have found it :) I would have probably searched whole day long. As a related question, Is there any way to debug SDM and AppEngine server > at the

IntelliJ 15, SuperDevMode, AppEngine, Gradle

Hey guys, I'm starting a new GWT project and, seeing as how we're on the precipice of GWT 2.8 with JsInterop, I've decided to try to get myself together and upgrade my project and setup. It's a fresh project, but I had a working Eclipse version based on GWT-Views and some OAuth stuff. I've

Re: IntelliJ 15, SuperDevMode, AppEngine, Gradle

> 1. If I'm using AppEngine and SDM, do I need to have to separate debug > configurations? One for SDM and one for AppEngine? Then start them one > after the other? > Never used AppEngine but I would generally say yes since you most likely launch SDM with -noserver when using AppEngine

Re: SuperDevMode and same origin policy

> Thomas, you are right. I had some conditional logic which chose which > scripts should be loaded in production or dev mode (original or minified > and merged) but I used GWT.isProdMode() and forgot that in SDM it returns > true... Sorry for that. > You can use the following in your

Re: SuperDevMode and same origin policy

Thomas, you are right. I had some conditional logic which chose which scripts should be loaded in production or dev mode (original or minified and merged) but I used GWT.isProdMode() and forgot that in SDM it returns true... Sorry for that. On Thursday, October 22, 2015 at 10:36:57 PM UTC+2,

Re: SuperDevMode and same origin policy

hat in SDM it returns >> true... Sorry for that. >> > > You can use the following in your condition: > > public static boolean isSDM() { > return GWT.isScript() && !GWT.getModuleBaseForStaticFiles().equals(GWT. > getModuleBaseURL()); > } > > >

Re: SuperDevMode and same origin policy

Thanks JonL, I'm aware of CORS headers, but unfortunately this case is different. Currently WebWorker will not start if it's not in the same origin as the context that wants to start it... According to the spec it should start in different security context but that's not yet supported in

Re: SuperDevMode and same origin policy

Aren't public sources copied to launcherDir on startup? Isn't it possible to load the files from the appropriate origin? -- 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

Re: SuperDevMode and same origin policy

Greg, You can create a filter that will set the appropriate headers for things served from the CodeServer with a filter like the one below (from https://spring.io/guides/gs/rest-service-cors/) . public class SimpleCORSFilter implements Filter { public void doFilter(ServletRequest

Re: SuperDevMode and same origin policy

Hi This is an old thread but I have similar SOP issue: I have a host page in the root of the webapp: /index.html I also have a web worker on public path which ends up in /worker/Name.worker.js I'm starting the worker using 'new Worker(); which is based on GWT.getModuleBaseUrlForStaticFiles();

Re: Removing the SuperDevMode code server prompt

One question remains unanswered: how are you launching SDM / loading the page that you're facing this dialog box? IIRC, the reason it doesn't automatically reloads is to avoid hiding the fact that the CodeServer isn't running at all (and you'd wait forever). I'd suggest deep-diving in the

Re: Removing the SuperDevMode code server prompt

I'm using the Netbeans GWT plugin. On 14 October 2015 at 08:20, Thomas Broyer wrote: > One question remains unanswered: how are you launching SDM / loading the > page that you're facing this dialog box? > > IIRC, the reason it doesn't automatically reloads is to avoid hiding

Re: Removing the SuperDevMode code server prompt

This is the dialog I mean: On Monday, 28 September 2015 09:23:18 UTC+1, Jens wrote: > > > That sounds like what I have been after. I can't see that feature in the >> 2.7.0 download -

Re: Problems GWT2.7 superdevmode + tomcat server

Server-side is not GWT's deal. "Compile in load" is only about the client. -- 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

Re: Problems GWT2.7 superdevmode + tomcat server

I have one more question regarding this issue, I don't know if it is normal superdevmode behavior or I am doing something wrong : When I make a change to my war/META-INF/context.xml file and hit F5 in the web browser, the changes are not taken into account (even if I force a recompile

Re: Problems GWT2.7 superdevmode + tomcat server

Thanks Thomas, I found some time to work on this issue and it is working fine. To get the unpacked war directory I did unzip the war file. My CodeServer debug launcher has 3 args: -src, -launcherDir, and the GWT module. -- You received this message because you are subscribed to the Google

Re: Removing the SuperDevMode code server prompt

> That sounds like what I have been after. I can't see that feature in the > 2.7.0 download - is it in the 2.8 builds? > I would say so as I use it and never had an issue with any prompts. -- J. -- You received this message because you are subscribed to the Google Groups "GWT Users"

Re: Removing the SuperDevMode code server prompt

On Monday, September 28, 2015 at 10:23:18 AM UTC+2, Jens wrote: > > > That sounds like what I have been after. I can't see that feature in the >> 2.7.0 download - is it in the 2.8 builds? >> > > I would say so as I use it and never had an issue with any prompts. > Actually no. It is in 2.7

Re: Removing the SuperDevMode code server prompt

> Actually no. It is in 2.7 [1], and has since been made synchronous [2] (so > you possibly wait a little longer). > > But if you're using CodeServer rather than DevMode, you have to wait > before loading the page; that code is only about enabling the "Launch > Default Browser" and "Copy to

  1   2   3   4   5   >