Sorry, as I wrote that last response, I realized that I was incorrect.
Reflection does not come into play when dealing with GWT RPC types, since
GWT's RPC servlet must know about all possible types that could be sent
across the wire.
I believe that GWT's RPC generator will compute the exact set of
Hey Thomas,
Responses inline:
On Wed, Jun 24, 2009 at 12:19 PM, Thomas Broyer wrote:
>
>
>
> On 24 juin, 17:00, Rajeev Dayal wrote:
> > Hi Clanusse,
> >
> > You are right - the only class files that are needed are those that are
> used
> > by RPC, which are:
> >
> > -your sync interface
> > -an
On 24 juin, 17:00, Rajeev Dayal wrote:
> Hi Clanusse,
>
> You are right - the only class files that are needed are those that are used
> by RPC, which are:
>
> -your sync interface
> -any types that can be passed across the wire over RPC
> -your server-side classes (including the implementation
Hi Clanusse,
You are right - the only class files that are needed are those that are used
by RPC, which are:
-your sync interface
-any types that can be passed across the wire over RPC
-your server-side classes (including the implementation of your sync
interface)
Unfortunately, the plugin's dep
I'm using Eclipse with the Google GAE/GWT plugin to build a combined
GAE/GWT project. I've noticed that Eclipse builds all my classes and
places them in the war/WEB-INF/classes directory even if they are just
GWT client code that also gets crossed compiled to javascript.
Is this necessary for de
