Loading extensions in static inner classes from shaded JAR files #229
-
Hi, Thanks for the nicely-featured library, it's made Guice/Dropwizard integration a lot more painless for me. I do run into an issue using class path scanning to load a Jersey extension from my app's shaded JAR. I traced it into This doesn't really work in my case, where I use a shaded JAR for my app. Is there anything obvious I'm missing in this behavior or is this a bug in Thanks, |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 4 replies
-
Hi! Could you please better describe your issue: is it exception during classpath scan or inner class gets resolved as an extension or an opposite (extension not recognized)? As a general rule I always propose to use classpath scan only on classes in the current project (simply because it's faster for development). If something moved to external jar (module) it's better to register such extensions manually with a bundle (when custom bundle inclusion is possible). Still, just a recommendation, not a requirement. Will be able to tell more with new details |
Beta Was this translation helpful? Give feedback.
Hi!
Could you please better describe your issue: is it exception during classpath scan or inner class gets resolved as an extension or an opposite (extension not recognized)?
Small example would also be helpful (to understand what kind of path was accepted (or not))
As a general rule I always propose to use classpath scan only on classes in the current project (simply because it's faster for development). If something moved to external jar (module) it's better to register such extensions manually with a bundle (when custom bundle inclusion is possible). Still, just a recommendation, not a requirement.
Will be able to tell more with new details