Hi Sundeep,
I have been doing this for quite some time and it seems the best
way is to split things out this way;
Common project (I call these projects Models as well)
Contains RPC Interfaces and Models(pojos with getters and setters)
Server project depends on Common project
Contains Servlets, HttpFilters and other server side stuff
Client (GWT) project depends on Common project
Contains actual GWT code
your_project/war directory and content web.xml exc
I have been using this for quite a while with the Google plugin for
Eclipse, deploying on JBoss and GAE (Google App Engine) and it seems
to work well.
You can then right click on the Client project from eclipse and
run as a web app (Google plugin for Eclipse). Your build system will
need to copy the Common.jar and Server.jar into your Client/web/WEB-
INF/lib directory.
Cheers,
Scott
On Oct 29, 12:42 pm, "Sudeep S" <[email protected]> wrote:
> Hello,
>
> Can someone suggest the techniques/best practices involved in packaging the
> GWT applications where the client code and server code reside separately.
>
> Thanks
>
> Sudeep
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
