>I am running some RMI applications on a machine which doesn't have
>the necessary classes installed -- the RMI class loader runs out and
>grabs the ones that are needed, using the codebase property. That
>works great.
Yay mobile code!
>I wonder if I will have to obtain the javac source and hack it to use
>RMIClassloader.loadClass instead of Class.newInstance or something
>like that.
I think you could just build a new javac that has a different
ClassLoader. Someone might have even done this already, it's sort of
obvious. javac itself is trivial, all the real work is in
java.lang.Compiler and its friends.
One thing that's complicated, though - the Java compiler loads .java
files as well as .class files. The ClassLoader doesn't, as far as I
know. So the logic might be a bit screwy.
