Edgar and Jon.
I have decided to just use a text file containing the name of each class
that
I need to load and the create and object from.
Although this requires a little more effort to install the plug-in, it is a
whole lot
easier to program. I'll probably write a little helper class that appe
Hello Sunburned,
also to minimize the jars searched on you might instantiate a new
Classloader (e.g. java.net.URLClassLoader) containing only a few
selected jars e.g. in some folder or so. I found examples using a
classloader with some other api classes to find classes by interface or
implemen
Jon,
That makes a lot of sense. Thanks for your explanation.
Landon
On 4/4/07, Jonathan Aquino <[EMAIL PROTECTED]> wrote:
If I remember correctly, for JUMP it was quite slow to determine this
programatically (I think you have to instantiate every class in the jar).
So instead we search base
If I remember correctly, for JUMP it was quite slow to determine this
programatically (I think you have to instantiate every class in the jar). So
instead we search based on the _name_ of the class, i.e., *PlugIn.class.
You should be able to do the same in your case if all classes that implement
