Linked by Eugenia Loli on Mon 27th Sep 2004 21:04 UTC
Permalink for comment
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/21/13 22:06 UTC
Linked by Thom Holwerda on 05/21/13 21:45 UTC
Linked by Thom Holwerda on 05/21/13 15:53 UTC
Linked by Thom Holwerda on 05/20/13 22:43 UTC
Linked by Thom Holwerda on 05/20/13 21:50 UTC
Linked by Thom Holwerda on 05/19/13 23:15 UTC
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
Linked by Thom Holwerda on 05/18/13 21:06 UTC
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
More News »
Sponsored Links



>One could come to the conclusion that even if an
>"JVM+JavaLibraries implementation" passes the tessuite it
>still could be incompatible with other JAVA environments.
The point is this: Sun + JCP (Java Community Process) define what the Java Platform is. This is, among the Java Language Spec and JVM Spec, defined in the TCK (the test suite for the standard library).
If a Java Platform implementation of some provider passes all the tests of this TCK... then it is compatible to Java.
In short, this just means that Java apps written for the Java Platform, run the same way as on Suns implementation.
This is what is desired: Say I develop my Java app on Linux with IBMs JDK, and I then execute it on, for instance, Windows with some Microsoft Java implementation; If the app works the same way on both systems, then everything is OK.
This is what the TCK tests.
Now: If the MS implementation comes with... for instance, APIs to easily integrate a Java app with COM (or whatever), then that's fine by me. I *don't* have to use it. And if someone uses it, they need to be aware that they create something MS specific.
BUT: if my Java app uses the RMI API, but the MS Java implementation doesn't ship RMI... then there's trouble, because Sun + JCP defined RMI to be part of the Java Platform.