ExtensionFinder#find(): difference in dealing with started plugins, why? #556
Unanswered
gjokiel-axway
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi,
I'm evaluating PF4J and I was surprised by some behavior. Before creating an issue, I wanted to discuss it first. 😄
The doc says this about started plugins:
This seems to be respected by the find methods that take a pluginId:
but not by
AbstractExtensionFinder#find(Class<T> type)
Do you know why this difference?
A little bit about what I wanted to do.
I have a bunch of plugins that implement the same extension and I wanted to load them all, then start only the one I need by its pluginId, then find the extension without the pluginId.
I know I can do otherwise and this is no big deal, but some consistency is always nice.
Thanks
PS: Nice piece of work by the way. The code is very clean 👍, which is nice.
Beta Was this translation helpful? Give feedback.
All reactions