Eric Clayberg wrote:Either option should work fine.
stsch77 wrote:Or first create a project with the plugin and then add the support for GWT Designer tools?
stsch77 wrote:I right-click on my GWT project --> Properties --> Google --> App Engine --> Check "Use Google App Engine" and then realize that the file "appengine-web.xml" plus some other mandatory/helpful files don't get generated and are missing
stsch77 wrote:The Run configuration gets overwritten, for example, in particular from com.google.appengine.tools.development.DevAppServerMain to com.google.gwt.dev.DevMode plus some other arguments to the program and the VM get changed. That's not what I want.
wittml wrote:I just installed GWT Designer 7.6.0 and was able to get app engine to work (easiest way) by:
1. Create an app engine/gwt project like normal.
2. Delete the default entry point.
3. Create an entry point using GWT designer.
Steps 2 and 3 probably could have been combined into one step as: Open your java client using the WindowBuilder editor.
deuce4 wrote:One glitch with the above method is that if you create the GWT/GAE project by the normal means, then use the WindowBuilder create RemoteService Wizard, the Async class does not get created. Odd, can't really see why it would work with a project created in WindowBuilder, verses a project created with the Google default tools, but it only seems to work in the former case.
Users browsing this forum: No registered users and 1 guest