-noserver and super dev mode source maps

[Brandon Donnelson]

I'm wonder what the process is for the GWT 2.7.0  -noserver program args configuration to access super dev mode source maps. I've seen the flag for the remote server to sync the rpc policy, but it appears this doesn't apply to SDM. 

I haven't had time to go into greater testing yet for this configuration and I'd like some help with any hidden flags I might be missing with a program args.

Could someone elaborate on your -noserver configurations for SDM and have you been able to get source maps to show up?

Thanks,

Brandon

[Thomas Broyer]

First, a disclaimer: I haven't really used 2.7 yet, so I'm speaking "theoretically "here.

Not sure what you really ask here. DevMode does 2 things: launch CodeServer with -launcherDir <warDir> and start an embedded Jetty serving <warDir> as a webapp.

With the -noserver flag, DevMode is thus equivalent to launching CodeServer with -launcherDir <warDir>, and you're supposed to launch your own servlet container to serve <warDir> as a webapp.

So how is that different from launching CodeServer and using the bookmarklets? The *.cache.js is served from CodeServer in all cases, as are the source maps.

So theoretically there's no reason using DevMode with -noserver to be the cause of source maps not showing.

[Brandon Donnelson]

Thank you that helps.

Have a good day,
Brandon Donnelson

+Follow Me

--
You received this message because you are subscribed to a topic in the Google Groups "Google Web Toolkit" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-web-toolkit/aV1Y13F-nEA/unsubscribe.
To unsubscribe from this group and all its topics, send an email to google-web-tool...@googlegroups.com.
To post to this group, send email to google-we...@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.