true, the static bloc is 10 LOC of boilerplate in 1.5/1.4 My app, has 20+ RPC interfaces, one per sub-system. They are all bound to ONE RPC interface, the Server takes care of dispatching to the right POJO that matches the RemoteInterface dynamically. 1.6 was just less boilerplate.
On Apr 11, 5:56 am, Vitali Lovich <vlov...@gmail.com> wrote: > Yeah, makes sense. I'd still do the log statement in the static initializer > just to be certain. > > I don't see how any of this actually new though with 1.6. You could have > done all this earlier as well with the appropriate code snippet going into > the static block. > > On Sat, Apr 11, 2009 at 5:38 AM, Dean S. Jones <deansjo...@gmail.com> wrote: > > > > > > > Yes, true - but in GWT, the ONLY reason to reference an Async class it > > to make an Async call... --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. 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 -~----------~----~----~----~------~----~------~--~---
