It's actually (and fortunately) easy: change gwt.codesvr in your URL with gwt.codesvr.moduleName, where "moduleName" is your module name (the one in your gwt.xml's rename-to="") That way, the third-party module won't try to run in DevMode, only your module that matches "moduleName".
On Thursday, October 11, 2012 3:35:45 PM UTC+2, Denero wrote: > > Hi, > I have a GWT application which uses a JavaScript library published on a > remote > server and that also was developed under GWT and the APIs exposed over > JSNI. I > do not have access to the source ocde of that. That library uses > cross-site > scripting and uses xsiframe linker option. > > My application which include that in a script node and calls its APIs > works fine > in the production mode. But now for some debugging purpose in my > application > when I run it in the dev mode, all the API calls to the other GWT library > fails > because it looks like it also trying to run in dev mode as I see that > *.devmode.js of that is getting loaded and thus that module is not loaded > successfully(I do not see any errors either). > > How can I run my application in dev mode while still keeping the other > library > in production mode(ie just like any other native code)? As said, the other > library itself is hosted on a different server and when running our > application > in devmode we specify only our module names, so I would expect it to work > bydefault. Is there a compiler or dev mode option that I can use here? > > I am using GWT 2.4.0. > > Thanks in advance, > dw > > > -- 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/-/IJzN2Z6tfawJ. 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.
