aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorDecebal Suiu <decebal.suiu@gmail.com>2014-03-10 13:28:42 +0200
committerDecebal Suiu <decebal.suiu@gmail.com>2014-03-10 13:28:42 +0200
commit87267155edb2425981281d4e4c5fe833ebca3d0f (patch)
treece2e9acdbc9037e5c262b77bc73a315476124148
parentb57f307e53623dab815f3dfb0817be5b5dd5f503 (diff)
downloadpf4j-87267155edb2425981281d4e4c5fe833ebca3d0f.tar.gz
pf4j-87267155edb2425981281d4e4c5fe833ebca3d0f.zip
add reference to Annotation Processing
-rw-r--r--README.md5
1 files changed, 4 insertions, 1 deletions
diff --git a/README.md b/README.md
index 240a4f9..ec87e2b 100644
--- a/README.md
+++ b/README.md
@@ -102,7 +102,10 @@ You can define an extension point in your application using **ExtensionPoint** i
}
Another important internal component is **ExtensionFinder** that describes how the plugin manager discovers extensions for the extensions points.
-**DefaultExtensionFinder** looks up extensions using **Extension** annotation. You can control extension instance creation overriding `createExtensionFactory` method from DefaultExtensionFinder.
+**DefaultExtensionFinder** looks up extensions using **Extension** annotation.
+DefaultExtensionFinder looks up extensions in all extensions index files `META-INF/extensions.idx`. PF4J uses Java Annotation Processing to process at compile time all classes annotated with @Extension and to produce the extensions index file.
+
+You can control extension instance creation overriding `createExtensionFactory` method from DefaultExtensionFinder.
public class WelcomePlugin extends Plugin {