Classloading issue in case of custom classloader usage #3227
Comments
|
@glassfishrobot Commented |
|
@glassfishrobot Commented Regards, |
|
@glassfishrobot Commented |
|
|
Soooo... this issue is still persisting for me. No comments from the authors? I need to load jersey resources from "modules" (not java 9 modules, just external JARs that are loaded at runtime), via a custom classloader for isolation (and some other reasons). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When Jersey is loaded via custom classloader it's failing with ClassNotFoundException:
The reason of such exception is that ServiceFinder(loaded by current custom classloader) is using current thread's context classloader for loading services and as a result such classes are not found. All those service classes are coming with current custom classloader and not available for thread's context classloader. What I'm asking for is to change such logic and do fallback to current classloader. Something like Validation library are doing - http://grepcode.com/file/repo1.maven.org/maven2/javax.validation/validation-api/1.1.0.Final/javax/validation/Validation.java?av=f
I already had email conversation with Marek Potociar regarding this clasloading issue and he agreed to look into fallback with own classloader usage.
Note, that javax.ws.rs.client.FactoryFinder is having the same problem.
Environment
Weblogic 12.1.3, Java7
Affected Versions
[2.19]
The text was updated successfully, but these errors were encountered: