What’s a good way of adding a plugin interface such that it’s possible to have optional components?
I’m aware of the Class.forName() approach (used with JDBC for example) but there is also this approach to dynamic class loading.
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
What’s a good way of adding a plugin interface such that it’s possible to have optional components?
I’m aware of the Class.forName() approach (used with JDBC for example) but there is also this approach to dynamic class loading.
You may have a look at this: http://jpf.sourceforge.net/.
A good approach would be to load jar files in a specified directory at runtime and look if they contain plugin classes. Have a look at this: How to load a jar file at runtime.