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
transfor
Thanks for replying Paul, after doing some more research I understand a
little bit better how the compiler to javascript works, it only transforms
to javascript the 'client' classes (duh!) so this fits perfectly well with
our standards, we have a clear separation between our client code and RPC
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
On 15/06/12 04:10, jfiallo wrote:
I'm fairly new to developing with GWT. I was wondering if there's a way to
'patch' an existing gwt application, that is: update just a portion of an app
that a customer might already be using (ex. a java class that was modified).
The simple answer is no. It's
Hello All,
I'm fairly new to developing with GWT. I was wondering if there's a way to
'patch' an existing gwt application, that is: update just a portion of an
app that a customer might already be using (ex. a java class that was
modified). Any ideas on how to accomplish this would be apprecia
