GWT exception : Deferred binding result type should not be abstract Or Rebind result must be a class
In GWT, when you get this error in hosted mode
Deferred binding result type should not be abstract
or
The following error while compiling
Rebind result must be a class
most likely you have forgot to extend your business interface from RemoteService. Therefore GWT engine is trying to instantiate the interface itself. That is , instead of
@RemoteServiceRelativePath("relativeServicePath")
public interface BusinessInterface extends RemoteService
you have written
@RemoteServiceRelativePath("relativeServicePath")
public interface BusinessInterface
2 Comments »
Leave a comment
About
This blog is about the solutions to some of the problems faced by me related to my work. Out of many problems I face during my day to day work I choose to write about only those which either consumed too much of my time or solutions which are tricky and not mentioned in the reference manuals or tutorials of those technologies. This is just an attempt to save some of your precious time if you happen to face the same problem.
That is the primary purpose of this blog. But occasionally I write my thoughts and my comments about various technologies I come across.
This blog will eventually move to my new blog www.blog.parasjain.net at my new website www.parasjain.net
About Me
I am Paras Jain. I am a JEE developer working in Reston, VA, US. I am working in technologies like Spring, Hibernate, Groovy/Grails, Alfresco, Liferay, JSF, JBoss Seam, DWR, Jquery etc. Other technologies on which I have worked are Struts, C#.net, VB.net, Perl, Maven, JRun, WebServices etc.
I am Sun Certified Java Professional.
You can reach me at “Paras Jain”
-
Archives
- October 2009 (2)
- September 2009 (3)
- August 2009 (2)
- July 2009 (1)
- June 2009 (2)
- May 2009 (3)
- April 2009 (8)
- February 2009 (2)
- December 2008 (1)
- November 2008 (3)
- October 2008 (1)
- January 2008 (8)
-
Categories
-
RSS
Entries RSS
Comments RSS
It is exactly the other way around, but you have highlighted the right place in the code where the error comes from. Thank you.
Now the original post has been corrected and my previous comment is obsolete. Thanks again to the author for uncovering the cause of this error.