Stefano Mazzocchi wrote:
Being a sucker for statistics and charts, I've decided to look into
japitools myself and regenerate the graph of API coverage progress of
harmony.
In doing so, I started to familiarize myself with the Japitools and I
found a few interesting discoveries: the latest version of the three
freely available certified java 5 implementations (Sun's, BEA's and
IBM's) are *NOT* 100% compatible.
This is interesting..
[SNIP]
- o -
First the not-so-shocking things:
1) IBM ships with xpath support with DOM, while Sun does not. Is this
true of it's a bug?
2) IBM has a 'stub' subpackage of org.omg that Sun does not have
but the real shocker is that japitools reports that IBM has *modified*
the java.lang.StringBuilder class and added *15* new methods to it!
If this is true, how is it possible for this JVM to pass the TCK if you
add methods to a java.lang class? Isn't this the kind of stuff that TCKs
are supposed to prevent? Can anybody explain to me if this is true or if
this is a japi bug?
I was under the impression as well that there are signature tests to
ensure that APIs are complete and don't extend. Very interesting.
IIRC, there were in the other TCKs I've used.
geir
