🚀 go-pugleaf

As other people wrote to ask more questions about this personally, I found a
few moments to knock up an example plugin loader for an app that requires
adding plugins without too much configuration hassle.... There is a
jbuilder4 project in there for convenience.

http://www.softcomms.com/java/plugin.zip

It only does the first part of the job which is scanning a plugins directory
for plugin config files and the calling back the PluginContext (which in
reality would be the host applications that needs plugins). From this point
on it would get very application specific and more complex. There is a demo
app class which uses the loader but doesn't do anything interesting with the
config info. Any zip or directory placed in the plugins directory that has a
META-INF/plugin.properties file will be assumed to be a plugin and the host
app will get notified.

Just unzip into a new directory and run the demo class
com.softcomms.plugin.PluginDemo

You should see some output which indicates finding the extra 2 zip files in
the plugins directory (which would in reality contain more classes and
resources etc)... i.e

D:\JBuilder4\jdk1.3\bin\javaw -classpath
"C:\dev\Plugin\lib;D:\JBuilder4\jdk1.3\demo\jfc\Java2D\Java2Demo.jar;D:\JBui
lder4\jdk1.3\jre\lib\i18n.jar;D:\JBuilder4\jdk1.3\jre\lib\jaws.jar;D:\JBuild
er4\jdk1.3\jre\lib\rt.jar;D:\JBuilder4\jdk1.3\jre\lib\sunrsasign.jar;D:\JBui
lder4\jdk1.3\lib\dt.jar;D:\JBuilder4\jdk1.3\lib\tools.jar"
com.softcomms.plugin.PluginDemo

Plugin found by loader com.softcomms.plugin.PluginLoader@55af5
Plugin properties: {my.plugin.name=My Plugin!, my.plugin.class=MyPluginImpl}
Plugin found by loader com.softcomms.plugin.PluginLoader@55af5
Plugin properties: {my.plugin.name=My Plugin!, my.plugin.class=MyPluginImpl}

Hope this helps,
John
----------------------------
SoftComms Ltd.
110 Bonchurch Road
Brighton BN2 3PH
UK
Tel/Fax: + 44 (0)1273 600 785
http://www.softcomms.com