-
-
Notifications
You must be signed in to change notification settings - Fork 550
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to detect Extensions #82
Comments
The log of pf4j is very detailed on debug and you can see where is the problem (you can see what classes are loaded by each plugin class loader). |
I think @decebals has the right of it here. If you have a type |
Sorry my bad. |
No problem. Maybe it's the time to add o possibility in code to detect these situations. |
I am facing similar problem. @decebals How can access the logs for pf4j? |
I have followed the procedure outlined in the home page.
When the EAR is deployed and starts up in Wildfly, I can see that the ZIP file is unzipped. The manifest seems to be correct, and the extensions.idx has the class name.
Please let me know if you require any additional information to help me with this issue.
Thanks and Best Regards,
GPN
The text was updated successfully, but these errors were encountered: