On 0, Ola Lundqvist <[EMAIL PROTECTED]> wrote: > > No Class-Path at all whenever possible.. remember the example that Xalan2 > > provides a Xalan1-compatibility layer - it Xalan2 must be included, we can > > satisfy all Xalan1-dependencies with that library (with lower precedence). > > Not possible with Class-Path because the JVM adds the Classpath, not us. > > > > Ok, but what will happen to the applet-developers? Will it work anyway?
Applet developers can't expect any libraries except the Java core libraries to be installed. They have to provide their libraries on their servers or by Java extensions. Unless something like Jeff's idea gets mainstream and gets included in all JDK's, we don't have a chance. We cannot manipulate an applet's classpath because we can't create wrapper scripts for applets. One idea would be to create a mapping from Java Extension to our classpath. If an applet by Extension says it requires 'Xerces', we may give him the installed xerces-1.4.3 instead of downloading the Extension. Still, we would have to modify JavaPlugin for that. And additionally, that's very dangerous - although if we implement everything correctly, someone may come with an applet with broken manifest, and it runs on IE/Windows fine - but not on Debian because we're the only ones who do it right. Sadly, such things happen too often. I say, Applet developers may use Class-Path or Java Extension like they used to, we can't do anything here. > PS. You forgot the list again. :) Hehe, yes.. I'm getting used to it slowly :-) I reposted the mail 30 seconds later to the list Regards, Max
