Hi, I'll describe how I do it. Feel free to ask more questions. My development environment is Debian.
The GWT web server is an embedded version of Tomcat. AFAIK, it can't run Perl. So, you'll have to provide your own web server for testing the script. Where you go from here depends on whether or not you're using an IDE, in that your IDE will assist in the compile/link and will provide directories that are involved in the following steps: 1. You'll want to import your Perl script(s) into the IDE; 2. You run a compile/link step using the built-in server. You can't invoke your external server until you've created the Javascript. This step creates the Javascript. 3. These scripts will be copied to an output directory as part of the GWT compile/link step along with other static files (entry HTML file, images, CSS files, &c) 4. You copy these scripts from either the IDE internal directory or from the output directory to your /var/www directory; 5. You tell GWT to use your server. This is a modification to the compile script. My command line arguments are as follows: -out www # step three directory (mandatory) -style detailed # makes Javascript debugging easier (optional) -noserver # tell GWT to use an external server (mandatory) -port 4000 # tell GWT which server port to use (optional, although you'll have to configure your server to use the GWT default) equine/Equine.html # URL (mandatory) 6. Test your Java code using the GWT shell. The Java code will invoke the external server which will then invoke your Perl script. The external server will not run the Javascript. 7. Perform steps two, three and four then test your code using a stand- alone browser and the URL (don't forget the port) from step 5. This will test the Perl script and also the Javascript. If you used the - style switch with the "detailed" or "pretty" arguements, you can easily set breakpoints &c using Firebug or whatever Javascript debugger IE uses. See also http://code.google.com/docreader/#p=google-web-toolkit-doc-1-5&s=google-web-toolkit-doc-1-5&t=FAQ_HostedModeNoServer for more information. Step one occurs only once Step two occurs at least once Step three occurs automatically as part of a compile/link step Step four only occurs each time you change the CGI script Step five occurs only once This isn't trivial, but it's quite doable. One annoying gotcha (in the sense that I keep forgetting) is that after a GWT upgrade, you have to re-run step two. For this reason, I keep two build scripts: one that invokes the built-in server, and one that invokes the external server. On Dec 11, 11:51 am, sssmack <jimc...@gmail.com> wrote: > I imagine the cgi should be put into the www area/directory but I > don't know how to set this up. > Please give me a link that will help me or try and describe how to do > this. > > Thanks --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to Google-Web-Toolkit@googlegroups.com To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
