On Fri, Apr 16, 2010 at 4:51 PM, <[email protected]> wrote: > Done. Basically it's a complication becuase we use different > classloaders to load the script-only classes vs. the non script-only > ones. I don't understand why it was chosen as it imposes extra > constraints on how the @GwtScriptOnly class can be used (e.g. access to > package private members). > > I wish the same classloader could be used to load all classes.
Yeah, this seems bad to me. We should be using GwtScriptOnly just to decide which bytes to use; the actually bytes (once found) should always get loaded into the same class loader. Can you look into this or ask Bob? Scott -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
