Niclas Hedhman wrote:
> Because downloading class files via http is so much more effecient,
> and hosting those via http left the RMI team to focus on more
> important stuff.
> Personally, I employed one out of two strategies to deal with
> dynamically loaded classes (I'm sure there are others);
> 1. Either embed a tiny http server in each service, and all classes
> are picked up from the originating host. Requires a little bit of
> trickery, since it is (or at least was) not possible to specify http:
> URLs in the classpath on the command-line. And basically, the
> bootstrap code would launch the http server, and then create a new
> classloader with the real application's classes pointed out via a
> http:// to the current running machine.
The RMIClassLoaderSPI is meant to take care of this issue by allowing you to
specify a classloader that will provide the appropriate annotations.