I believe you are correct about the ClassLoader assumption on the part of the SDK. In this article: https://jaxb.java.net/faq/, they explain that in the case of many web applications, you need to explicitly pass the ClassLoader to the jaxb library. I tried to find a workaround to add my own ClassLoader to the jaxb library with no such luck. I'm attempting to file a support request for this fix. My code works from a Java application, but not from the Hudson Plugin that I'm trying to build, so this is the only thing I can think as to why it would work one place and not the other. I also tried the FakeSSLFactory workaround, which didn't fix the issue for me.
↧