From 198949b8b08b79cb4e3ae69aa9fcb1969bb7acf9 Mon Sep 17 00:00:00 2001 From: Decebal Suiu Date: Fri, 4 Oct 2013 11:35:10 +0300 Subject: [PATCH] Update README.md --- README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index a7bc2af..e11b750 100644 --- a/README.md +++ b/README.md @@ -101,7 +101,7 @@ You can define an extension point in your application using **ExtensionPoint** i } -Another important internal component is **ExtensionFinder** that describes how plugin manager discovers extensions for extensions points. +Another important internal component is **ExtensionFinder** that describes how the plugin manager discovers extensions for the extensions points. **DefaultExtensionFinder** is a "link" to **SezpozExtensionFinder** that looks up extensions using **Extension** annotation. public class WelcomePlugin extends Plugin { @@ -135,7 +135,7 @@ The output is: >>> Welcome >>> Hello -You can inject your custom component (for example PluginDescriptorFinder, ExtensionFinder, PluginClasspath, ...) in DefaultPluginManager just override createXXX methods (factory method pattern). +You can inject your custom component (for example PluginDescriptorFinder, ExtensionFinder, PluginClasspath, ...) in DefaultPluginManager just override `create...` methods (factory method pattern). Example: @@ -154,7 +154,7 @@ and in plugin respository you must have a plugin.properties file with the below For more information please see the demo sources. -Development runtime mode +Development mode -------------------------- PF4J can run in two modes: **DEVELOPMENT** and **DEPLOYMENT**. The DEPLOYMENT(default) mode is the standard workflow for plugins creation: create a new maven module for each plugin, codding the plugin (declares new extension points and/or -- 2.39.5