Hi all.  I'm new to GWT and its Eclipse plugin.  I was hoping to get some 
advice on how to approach making a small GWT app and integrating it into an 
existing Java EE website.

The first thing I noticed when I made my first GWT app, "FirstGWT", was the 
web application with the plugin used that name, /firstgwt, for the path to 
all of the generated JavaScript code.  So I was thinking that a longer path 
than just right off the web root would be appropriate in the long run, like 
/api/apps/firstgwt for example.  

Is there a way to change the path the plugin made?  Can I just copy the .js 
code to another directory/path on my websever and everything will just 
work, or the path /firstgwt embedded in the various scripts and other 
components?  What would recommend to meet the goal of a more flexible 
server side path (especially if the final path isn't known during 
development, for example)?

OK, next question is regarding the sever side stuff.  I assume I can place 
the GWT servlets in a jar/war file and place it in the /lib directory of 
the final war/ear file I deploy.  Is that true?  What files besides just 
the servlets should I include?  What does GWT need to configure itself, for 
example?

That's it for now, I think.  Hopefully soon I'll get a better grasp on how 
GWT fits into the larger picture of web development.  Thanks for helping 
out if you can.


-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to