Re: Strange runtime error: AbstractMethodError
"Mike Schilling" <mscottschilling@hotmail.com> wrote in message
news:pWqyh.25398$yC5.9050@newssvr27.news.prodigy.net...
It is axiomatic that AbstractMethodError means that something changed
between compilation time and runtime. If you could recompile the whole
thing from source, then either your problem would go away or you'd see a
compilation error that explains the problem.
Or that there's a bug in the compiler/JVM? ;) Elsewhere in this thread,
I've posted an SSCCE that doesn't require the Saxon JAR, compiled it
completely from scratch, and got the same error message.
My guess is that some of the definitions of getParent() are incompatible
(i.e. return different types), but that's just a guess. It's a place to
start though: what type does Token.getParent return? The overload that
can't be found returns net.sf.saxon.om.NodeInfo
Right. If you take a look at the new SSCCE, getParent() (now renamed
"someMethod") is defined twice, each one with a different return type. But I
thought this was legal in Java... "Return Type Covariance", it's called, or
something like that, right?
- Oliver