> That class is part of our module, and obviously it exists. > How can I solve that problem?
Well, just as obviously, it's not accessible to the classloader that's trying to load it. The failing line of code is Class cls = Class.forName(clsName); which is equivalent to Class cls = Class.forName(clsName, true, this.getClass().getClassLoader()) so your class needs to be accessible to the classloader that loaded GEF/PGML. The answer will probably also depend on your execution environment (Eclipse vs Ant vs Java Web Start) and the packaging of your plugin module. Since plugin modules are loaded explicitly by the plugin module loaders (either the old-style loader or the new-style loader), they potentially could be visible to the module loader, but not to a classloader. If this is the problem, one possible workaround would be to explicitly load your Fig class at module initialization time. You'll probably want to read a little bit about classloaders to understand better how they work and what the potential problem areas are in your application. They're complex enough that just hacking at things blindly is likely to be a long and frustrating process. Tom p.s. It looks like your manifest was copied from someplace else without updating it for your application. You might want to update Implementation-Title, Implementation-Version, and Implementation-Vendor which clearly refer to a different plugin. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
