I just like to address your reference to Kaffe being a personal java
environment.
After lurking a while on this list, I'm starting to realize that Kaffe's
labeling as "PersonalJava" is an unfortunate one.
PersonalJava (http://www.javasoft.com/products/personaljava/)
http://www.javasoft.com/products/personaljava/spec-1-1-1/pjae-spec.html
is a Sun product and specification for a subset of Java. This subset
is roughly equivalent to Java 1.1.x, although some packages' API has
been minimally changed and many packages, such as java.security or
java.math, have been marked as "optional"---whatever that means.
Kaffe (www.kaffe.org), on the other hand, strives to be a fully
functional replacement for a Java 2 VM and its class libraries. However,
it's not quite there yet. Realistically, it is mostly a Java 1.1 VM
with support for some 1.2 classes, and it is lacking a few 1.1 packages
(incidentally, it's missing java.security which PersonalJava marks as
"optional" --- so I guess it makes some sense.)
In some cases where Kaffe does not provide its own implementation, you can
simply use another implementation. For instance, Kaffe
does not provide a replacement for the servlet API JSDK2.x, but you
can use Paul Siegman's or even Sun's package for that.
Similarly, you can often use Sun's classes if they are written in
100% pure Java. Those parts of Sun's libraries that are not 100% pure
Java --- namely those relying on classes in sun.* --- don't usually
work if they require native methods. They sometimes don't even work if they
do not require native methods, but use other backdoor interfaces.
For instance, sun.io.CharToByteConverter is a classical example for an
undocumented interface implemented outside the Java API. Sun does not
give you a way to implement your own converters.
To use Sun's classes with Kaffe, all that's needed is to copy a
1.1 classes.zip into the same directory that contains Kaffe's Klasses.jar,
and Kaffe's driver will pick it up.
If you try your application with Kaffe, and you find that it does not
run to your satisfaction, you're encouraged to file a bug report with the
bug database at www.kaffe.org. If it is a 1.1 app that does not use
security, it should run. If it's a 1.2 app, we'd still like to know how
it fails: this will give us an impression of which 1.2 packages people
use to give them more priority.
To address your question regarding memory requirements, Kaffe can run
simple applets in its appletviewer with a 2 MB heap. This does not
include the code of its VM and supporting native and other libraries
(which are in separate shared libraries) For more details, see
http://rufus.w3.org/tools/Kaffe/messages/5127.html
http://rufus.w3.org/tools/Kaffe/messages/5130.html
I hope that helps,
- Godmar
----------------------------------------------------------------------
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
