Just to make some more noise on this discussion, I put together an alternate GWT plugin a few months ago. I have been using it to make web applications; in other words, the GWT-based stuff is part of the WAR file that is generated by my project. The project I have been working on has a number of servlets which are used by the front-end created by GWT. My plugin is set up to use the GWTshell for development testing (try "mvn gwt:shell") and the project builds the GWT stuff as part of assembling the WAR file.

If anyone wants to take a look at it, you can find the plugin project at http://www.sd.no-ip.biz/gwt-plugin.tar.gz. You can find a project that uses the plugin at http://www.sd.no-ip.biz/gwt-project.tar.gz. You can see the application in action at https://www.sd.no-ip.biz/plants/ but you need to tell your browser that you accept my self-signed certificate. The application currently runs on fixed data supplied by the servlets, not the front-end; the GWT stuff has to call back to the servlets to get the data to display. You can enter anything you want to login to the application; since I am just testing right now its much easier if I don't have to bother with typing usernames and passwords for every test.

I am willing to answer questions and help people get things running. (If you ask questions about how to get the plugin working, my answers are limited to the plugin I wrote. ;-) If the author of the current GWT plugin doesn't mind their stuff being overwritten, I can get a better plugin (mine or someone else's or a mix) into Codehaus so more people can use it.

----- Original Message ----- From: "J. Matthew Pryor" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Wednesday, January 31, 2007 6:02 PM
Subject: [mojo-dev] gwt-maven-plugin - making webapps work with GWTShell


I have found a few issues trying to use the async servlets with a non trivial webapp.
When I run using gwt:run, there are missing dependencies.

I found that the command-line generated by GWTRunMojo needs to include all dependencies, not just "sources" dependencies.

Also I found that the ${project.build.directory} needs to be added to the GWTShell classpath.

These are pretty simple code changes to make, but I wondered if perhaps I was doing something wrong.

In particular I was using xstream with the servlet and although xstream was in the deps for my maven project, GWTShell fails to load the servlet properly.

Adding xstream to the classpath does the trick

Cheers,
Matthew

---------------------------------------------------------------------
To unsubscribe from this list please visit:

   http://xircles.codehaus.org/manage_email




---------------------------------------------------------------------
To unsubscribe from this list please visit:

   http://xircles.codehaus.org/manage_email

Reply via email to