Sunday, May 30, 2010

Re: GWT.runAsync and Command Pattern

yes
also i've faced this problem and didn't find any solution
i'think the previous issue it's connected with this:

http://code.google.com/p/google-web-toolkit/issues/detail?id=2374&can=5

On 30 Mag, 15:48, Tristan <tristan.slomin...@gmail.com> wrote:
> You might be running into this issue:
>
> http://code.google.com/p/google-web-toolkit/issues/detail?id=4412
>
> The compiler simply doesn't do enough analysis to do code split
> properly when inheritance is involved, staring the issue may help.
>
> Cheers
>
> On May 30, 7:38 am, Julio Faerman <jfaer...@gmail.com> wrote:
>
>
>
> > Hi,
>
> > I am trying to split a GWT app that uses the command (action) pattern.
> > The problem is that  "GWT.create(ActionService.class)" causes every
> > subclass of the return and parameter types to be included in the
> > initial fragment.
>
> > For instance, my action interface is:
>
> > public interface ActionService extends RemoteService {
> >         <T extends Response, V extends Request> T execute(V req) throws
> > ActionFailedException;
>
> > }
>
> > the problem is that "module1.SomeRequest" and "module2.OtherRequest"
> > gets included in the initial fragment.
> > Do you see a way around this?
>
> > Thanks,
> > Julio Faerman

--
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+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.

No comments:

Post a Comment