Forums
New posts
Search forums
Members
Current visitors
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Menu
Log in
Register
Install the app
Install
Forums
Archive
Archive
Java
limitations of Class.forName
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
[QUOTE="Roedy Green, post: 5157613"] 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. [/QUOTE]
Verification
Post reply
Forums
Archive
Archive
Java
limitations of Class.forName
Top