The title says it all, but how do I achieve it?

 - How will I structure, run, compile and deploy my gwt project? (I
want to keep it separate from my existing projects)

 - Will the generated WAR file, when deployed, overwrite the contents
of the existing WEB-INF/lib?

 - How do I get my rpc servlets put into a WEB-INF/lib/xx.jar file
instead of .class files in WEB-INF classes?

 - Why does the WAR file contain the com...client .class files? Why
not only the com...server .class files? What are their use?


Existing site:

 - The existing site has lots of business classes in WEB.inf/lib/
xx.jar

 - The GUI is built by 10-line jsp files reading business data and
tranforming to html via xslt.

 - Until now my work has been split into two eclipse projects;
 - - a java project with all the business-logic and
 - - a simple project with all the web related stuff (jsp, xslt, css,
web.xml etc.)


My background:

 - I know GWT very well (2 yrs client-side development, JSON interface
to services using -noserver to make everything work)

 - I know Tomcat/J2EE very well (but unfortunately I'm an ant novice)


The ultimate goal is a pure GWT frontend, with all jsp replaced by gwt-
rpc servlets serving data to be rendered by the client. I want to
start with a proof-of-concept and then gradually extend the
functionality of the GWT gui. I therefore need to find out how the two
different frontends can be maintained separately, but deployed
concurrently.

I'm NOT aiming for a transition phase with gwt widgets on my existing
pages, but for a second frontend built from scratch (Though I guess my
questions would be the same)


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/Google-Web-Toolkit?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to