java.lang.AbstractMethodError running a webapp in Eclipse with jetty. -
I am working on a project in Eclipse that when I use the JETI plugin, I
< Pre> java.lang.AbstractMethodError: au.com.mycopmpany.impl.MyClassDAOIpl.findById (Ljava / lang / Integer;) Ljava / lang / object;
This file is okay in Eclipse and is implementing the code method that talks about the error. This error indicates to me that "on the runtime" JVM gets a class that has not implemented this method.
But I can assure you that MyClassDAOImpl
does most definitely implement the findById
method with the correct signature.
This eclipse looks like a bug in the compiler; I can fix this problem by running the maven package
from the command prompt and then it works fine to run the app within the Elpsy.
It seems that there is some kind of bug in connection with the eclipse compiler. For this class, I had read something about online bug with the Eclase compiler (which uses this class generics) with generic , But this base class / interface has been re-implemented over and over in our code base and this is always a problem in this class. / P>
Does anyone know of an alternative solution to solve this problem, or better yet?
I can repeat this exception every time, so if any eclipse compiler developer reads it and it is known to the problem, please contact me to help keep an eye on this issue.
Update:
One of the many people implementing classes with this issue is Generic DAO
where the normal interface is Defined:
Public Interface Generic DOA & lt; T, TLIT & gt;
This method is in the unsuccessful question:
Public T findsById (integer integer) throws APIException;
Try remodeling your code
It looks like you've got a DAO interface, and the interface's signature and impression is slightly different that the compiler does not implement the interface completely by the solid impact class. Eclipse may be out of par.
If this does not work, then see if eclipse allows you to navigate through the interface method for concrete implementation. If this can not happen, then this is a clue that the compiler is telling you.
Check your CLASSPATH. It may be that you think this transplant is being loaded by JVM.
Check the bug list if you think this is a problem with the compiler.
If you do not see a bug in the list, assume that you have problems many people use it; A bug that was seriously searched and fixed long ago.
Clear Jetties Deployment - War and all temporary files can be reconstructed and redistributed that the JT is placed on the older version of the class file, which explains why it works on the command line And when you work on the web.
Let's say you get the problem first, last, and always.
Update: Is there a way to switch JDK that uses Eclipse? Can you point to Sun JDK?
This is another reason that I hate eclipses.
Question: Are you implementing it?
Comments
Post a Comment