From: <Ste...@lr...> - 2001-01-11 19:52:08
|
This is not a jEdit problem, just normal classloader operation. jEdit plugins are loaded via a custom classloader (org.gjt.sp.jedit.JARClassLoader). The JVM requires that if an object requests that a class be loaded, that it be done using the same classloader that loaded the referencing object. Therefore, the JVM expects the plugin classloader to load those classes, not the system classloader. The plugin classloader was not designed to load classes off the CLASSPATH. I'll echo Dirk's suggestion: all resources required by a plugin which are not already in jEdit should be in the plugin's JAR, or at least should all be in jar files in jEdit's "jars" directory. Steve Jakob kt...@mm... on 01/10/2001 02:54:01 PM Please respond to jed...@li... To: jed...@li... cc: (bcc: Steve Jakob/Lrcc) Subject: [ jEdit-devel ] JarClassLoader for Plugins I'm developing a Plugin which supports an RMI FileSystem. The Plugin references classes in a separate JAR file. When JEdit loads the Plugins, my plugin doesn't load because it can't find the separate JAR, although it is within the CLASSPATH directive. To remedy the problem short-term, I included all of the files in the separate JAR file into my Plugin JAR file. However, this doesn's seem to be very scalable. Am I missing something? or is this a limitation of JEdit's Plugin capability? Thanks, Kyley -- ----------------------------------------------- jEdit Developers' List jEd...@li... http://lists.sourceforge.net/mailman/listinfo/jedit-devel |