Groups > comp.lang.java.programmer > #28344

limitations of Class.forName

From	Roedy Green <see_website@mindprod.com.invalid>
Newsgroups	comp.lang.java.programmer
Subject	limitations of Class.forName
Date	2014-05-01 17:42 -0700
Organization	Canadian Mind Products
Message-ID	<p5q5m916vc7ued437313f6ghvac4slirrq@4ax.com> (permalink)

Show all headers | View raw

When I first encountered Java, I was very excited about the notion
of interfaces and dynamic loading. I thought it would let people plug
in their own code to every conceivable utility.

There are two catches. 

1. arranging that java.exe will look for your dynamic class in the
place where it is.  It will not usually be bundled in the original
jar.

2. arranging that java.exe will look for any auxiliary classes your
plugin needs in the place where they live.

A garden variety jar prevents java from looking anywhere else for
classes.

I thought I would write a short essay on this.  What techniques are
available?

I have always skirted the problem by putting all classes in the
original jar.
-- 
Roedy Green Canadian Mind Products http://mindprod.com
Computers are like Old Testament gods; lots of rules and no mercy. 
~ Joseph Campbell (born: 1904-03-26 died: 1987-10-31 at age: 83)

Back to comp.lang.java.programmer | Previous | Next — Next in thread | Find similar | Unroll thread

Thread

limitations of Class.forName Roedy Green <see_website@mindprod.com.invalid> - 2014-05-01 17:42 -0700
  Re: limitations of Class.forName Arne Vajhøj <arne@vajhoej.dk> - 2014-05-01 21:15 -0400
  Re: limitations of Class.forName Robert Klemme <shortcutter@googlemail.com> - 2014-05-02 08:51 +0200
  Re: limitations of Class.forName Josip Almasi <joe@vrspace.org> - 2014-05-02 09:25 +0200
    Re: limitations of Class.forName Roedy Green <see_website@mindprod.com.invalid> - 2014-05-06 03:55 -0700

csiph-web