> Happy coding,
> Scott, on behalf of the GWT team
Greetings:
Thanks for the tremendous efforts from GWT team and supporting
communities. Here are some preliminary exploration and wish list of the
coming doc:
1) Using the webAppCreator (ant 1.7.0, jdk 1.6) i create an application,
run the hosted mode, then the build to compile the app. In the app war
directory, i see the hosted.html and app.nocache.js, but Not the .css
and .html file as listed in the compiler output of the StockWatcher 1.6
example.
2) The current gwt-incubator_1-5_Dec_28.jar is not compatible with
GWT-1.6.0. Hope the new compatible version will be out soon. I am still
working through the examples to understand the new war structure,
especially the project that uses different modular GWT modules and the
location of public files for different modules. Some documentation and
suggested best practices may be required.
3) With new GWT Event Handler, the stockwatcher example shows a
container class to use a single handler method for event (ClickHandler)
coming from different event publishers (but1 and but2). GWT team may
share its experience and approach for all GWT event types in 1 container
class, especially the way to integrate GWT event handler with OpenAjax
Hub, leveraging GWT JSO and coming UIBinder ;-)
4) In the doc Articles and Tutorials, i see GWT for JSON Mashups and
Application of Facebook. It may be a good idea to centralize in 1 place
possible GWT applications and how-to to leverage Google API and
facilities: Gears, AppEngine, google-ajax-examples, etc.
Thanks
Duong BaTien
DBGROUPS and BudhNet
The difficulty arises when using Hosted Mode. First, I have to copy a modified web.xml to ${project}/tomcat/webapps/ROOT. This web.xml routes all requests to /services/* to my springDispatcher. This web.xml is different than the one I distribute with my WAR, since it also includes mapping for the GWTShellServlet. Also, in order for serialization to work, I have to compile my project once (using GWTCompiler) and copy all resulting *.gwt.rpc files to ${project}/tomcat/webapps/ROOT/${module}/. This occurs because the GWTShellServlet generates these dynamically as GWT-RPC requests arrive.
I've semi-automated the whole process using Ant tasks, and I'm aware of the gwt-maven plugin which provides some of this functionality, but I'd like to know whether the situation has been fully or partly addressed with the 1.6 release.
I'm not following... Do you mean for us to include these static
"Note that the
war directory is not only for compiler output; it is also intended to
contain handwritten static resources that you want to be included in
your
webapp alongside GWT modules (that is, things you'd want to version
control)."
resources in the compiler output directory and maintain this directory
under source control (with generated code alongside static source,
such as index.html and css files)? That seems like a bad idea to me.
Why not enforce the standard J2EE project path (see Sun's blueprints),
and maintain these files under /src/conf.
Congratulation for this release.
Unfortunately, there's still nothing about Maven support. No official
repository, no official plugin.... I hope this will arrive this
Milestone 2.
Regards,
Alexandre de Pellegrin
> 1) Backwards compatibility. If we updated JUnitShell to use HostedMode, itSo does this mean that GWTTestCases still spawns off a headless hosted
> seems like old test cases would probably break. The idea of a
> JUnitHostedMode is a good one... but how would we be able to tell which one
> the user meant, since the JUnit framework is in control?
mode that's using an embedded Tomcat and not an embedded Jetty?