Home/ Questions/Q 580319
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-13T14:27:36+00:00

I’d like to implement a dynamic plugin feature in a Java application. Ideally: The

  • 0

I’d like to implement a dynamic plugin feature in a Java application. Ideally:

  • The application would define an interface Plugin with a method like getCapabilities().
  • A plugin would be a JAR pluginX.jar containing a class PluginXImpl implementing Plugin (and maybe some others).
  • The user would put pluginX.jar in a special directory or set a configuration parameter pointing to it. The user should not necessarily have to include pluginX.jar in their classpath.
  • The application would find PluginXImpl (maybe via the JAR manifest, maybe by reflection) and add it to a registry.
  • The client could get an instance of PluginXImpl, e.g., by invoking a method like getPluginWithCapabilities("X"). The user should not necessarily have to know the name of the plugin.

I’ve got a sense I should be able to do this with peaberry, but I can’t make any sense of the documentation. I’ve invested some time in learning Guice, so my preferred answer would not be “use Spring Dynamic Modules.”

Can anybody give me a simple idea of how to go about doing this using Guice/peaberry, OSGi, or just plain Java?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    This is actually quite easy using plain Java means:

    Since you don’t want the user to configure the classpath before starting the application, I would first create a URLClassLoader with an array of URLs to the files in your plugin directory. Use File.listFiles to find all plugin jars and then File.toURI().toURL() to get a URL to each file. You should pass the system classloader (ClassLoader.getSystemClassLoader()) as a parent to your URLClassLoader.

    If the plugin jars contain a configuration file in META-INF/services as described in the API documentation for java.util.ServiceLoader, you can now use ServiceLoader.load(Plugin.class, myUrlClassLoader) to obatin a service loader for your Plugin interface and call iterator() on it to get instances of all configured Plugin implementations.

    You still have to provide your own wrapper around this to filter plugin capabilites, but that shouldn’t be too much trouble, I suppose.

    • 0