On 2/13/2011 6:13 PM, Calum Shaw-Mackay wrote:
What about using a standard html param that indicates the java version? Would this allow those that support this different version to be transparent for those services that support it, whilst allowing ensuring non-breaking compatibility with those services that don't provide multiple versions? How much work would need to be done to ClassServer to be able to support this?
The obvious answer is that this already works today. You can replace RMIClassLoaderSPI implementation in your JVM by overriding PreferredClassProvider use and return an annotation which includes such formulated URLs. You can then provide a web service handling such URLs and effect the appropriate activities therein to return the appropriate content.
Even smartproxies can be used to do this. They can look at the JVM they are running on, and then requires the appropriate proxy implementation service from the ServiceRegistrars which they know how to use.
Gregg Wonderly
