Hello I am having a similar issue.  The new version of the Eclipse
plugin throws an error because I have a base interface that all of my
remote service interfaces are based from.  It wants me to create an
async version of my base interface.

Is there a way to prevent this from throwing an error or should I
attempt to make a dummy or lose the base interface???


Thanks,
Rob



On Aug 4, 6:37 pm, Miguel Méndez <[email protected]> wrote:
> Version 1.1.0 checks GWT RPC interfaces.  Any interface that extends the
> RemoteService marker interface is considered to be a sync interface.  Once
> that happens it looks for an async interface.
>
>
>
> On Tue, Aug 4, 2009 at 6:09 PM, Tim McCormack <[email protected]> wrote:
>
> > When I updated Google Plugin for Eclipse from version 1.0.1 to 1.1.0,
> > my GWT project started throwing errors. I had a DataService class and
> > a DataServiceAsync class that were working fine, but GWT was claiming
> > that DataServiceAsync had an error and needed a DataServiceAsyncAsync.
>
> > In my case, the solution lay in editing the interface declaration.
> > Here's how DataServiceAsync used to start:
>
> > @RemoteServiceRelativePath("data")
> > public interface DataServiceAsync extends RemoteService {
>
> > I changed it to this:
>
> > public interface DataServiceAsync {
>
> > That fixed it! I suppose that this situation arose when I copied
> > DataService.java to DataServiceAsync.java and then fixed up the method
> > signatures and class name, but neglected to remove the annotation and
> > inheritence.
>
> > Apparently the older version of the plugin did not mind, but the newer
> > one does.
>
> --
> Miguel
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/Google-Web-Toolkit?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to