Well, I seem to be talking to myself here, but here's my fix in case anyone
else runs into this problem in the future. It's still a hack, but it
compiles a lot better than 1500 inner classes.
I updated the DeobfuscatorBuilder.java in requestfactory-apt-2.4.0.jar with
the following changes
Eric,
Please log this on the issue tracker and we'll look into it:
http://code.google.com/p/google-web-toolkit/issues/list
Thanks,
/dmc
On Wed, Sep 21, 2011 at 3:03 PM, Eric Andresen ericandre...@gmail.comwrote:
Well, I seem to be talking to myself here, but here's my fix in case anyone
else
Thanks, I have logged the issue as #6818 :
http://code.google.com/p/google-web-toolkit/issues/detail?id=6818
--
You received this message because you are subscribed to the Google Groups
Google Web Toolkit group.
To view this discussion on the web visit
Are there any tricks or tips to reduce the size of the 2.4 RequestFactory's
generated DeobfuscatorBuilder class? My compiler is choking with the
following error:
The code of constructor MyRequestFactoryDeobfuscatorBuilder() is exceeding
the 65535 bytes limit
The generated file is a single
I should note that my RequestFactory references about 120 Request objects,
each of which has between 5 and 20 methods. Would inheriting the Requests
off of a common base interface that defined the common methods work in the
RF? I'm not sure of the limitations of 2.4's RF inheritance.
--
You
I was able to somewhat unblock my testing using a sleazy workaround: I
re-compiled requestfactory-apt with a different DeobfuscatorBuilder that
generated the code as follows:
abstract class Command { public abstract void execute(); }
(new Command(){@Override public void execute()