Super Dev Mode only works with the xsiframe
linker, so make sure you have the following line in your .gwt.xml
too:
<add-linker name="xsiframe" />
That linker is safe for production use (Google uses it everywhere, slightly customized), so feel free to turn it on for all your projects (it combines the best of the std
linker –the default one– and the xs
linker, without their downsides).
Note: that linker will be the default in 2.7
If you use a version of GWT before 2.6.0, you'll also have to enable Super Dev Mode in your .gwt.xml
:
<set-configuration-property name="devModeRedirectEnabled" value="true" />
Otherwise, if you intend to use Super Dev Mode from a URL different from 127.0.0.1
or localhost
, then you'll have to whitelist the host. This is done using a regexp, e.g.:
<set-configuration-property name="devModeUrlWhitelistRegexp" value="http://(mymachinename|192\.168\.5\.151)(:\d+)?/.*" />
See https://dev59.com/QXzaa4cB1Zd3GeqPUcYU#21938574
compile and deploy your app to a web server near you (if you used a .gwt.xml
file specific to Super Dev Mode, make sure you compile that one module: the xsiframe
linker and devModeRedirectEnabled
property are necessary for that compilation step!)
If you use GWT-RPC, set the system property gwt.codeserver.port
to the port you'll run Super Dev Mode on (defaults to 9876
) so your server can download RPC serialization policies right from the Super Dev Mode.
If you run them on different machines, you'll have to override getCodeServerPolicyUrl
in all of your RemoteServiceServlet
s. Consider the security implications though, as noted in the javadoc