Thanks for the suggestion Joseph, out GWT app is basically just a front to our web services, so the RPC layer is the one consuming those and the dependent classes are there, on the gwt layer we only have lightweight classes to represent data and once these reach the server side we have transformers in place to perform the conversion into the relevant classes. It's very loosely coupled so we are fine with not being able to 'patch' only the presentation layer since the server side is not dependent on it and vice verse.
On Saturday, June 16, 2012 1:58:09 PM UTC-4, Joseph Lust wrote: > > Excellent question Juan, > > We are looking at a similar use case for a large GWT application. We are > considering breaking the application into standalone modules along GWT > module lines. These modules could then be compiled and deployed as separate > *war* files. Code common to many modules would be moved to a common > project and compiled to *jars* so that it could be a dependency of the > GWT modules (via Maven). > > This might suite your needs given that as long as you were not changing > code that would break an RPC (i.e. for shared module communications), you > could update that common project with your changes and recompile and > redeploy just the affected modules, not the entire app. > > Given that I'm still in the process of implementing the above > architecture, I'm curious if any other readers have faced/solved this issue > in large GWT apps? > > > Sincerely, > Joseph > -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/87o0Gtm47lQJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
