I’ve done this for software I’ve written in the past, it’s very handy. I did it by first creating an Interface that all my ‘plugin’ classes needed to implement. I then used the Java ClassLoader to load those classes and create instances of them. One way you can go about it is this: File dir … Read more
(Disclaimer: I am the author of JSPF, so better take my comment with a grain of salt 😉 The main reason I started with the JSPF was because I had the same problem as you have now: I was looking for a simple solution to make my thesis-project 1) extensible and 2) give it a … Read more
You may checkout the following blog post which is more adapted to Razor. But to answer your question, since you are now serving your views from a non standard location there is no longer the ~/Views/web.config file that applies and allows you to specify the base type for your razor views. So you might need … Read more
First you need an interface that all plugins need to implement, e.g. public interface Plugin { public void load(PluginConfiguration pluginConfiguration); public void run(); public void unload(); public JComponent getConfigurationPage(); } Plugin authors should then bundle their plugins into JAR files. Your applications opens the JAR file and could then use an attribute from JAR manifest … Read more
This is not an answer as much as a bunch of potentially useful remarks/examples. One effective way to make your application extensible is to expose its internals as a scripting language and write all the top level stuff in that language. This makes it quite modifiable and practically future proof (if your primitives are well … Read more