Null Pointer Exception from UnmarshallerFactory while migrating from OpenSAML2.x to OpenSAML3.x

[Brent Putman]

On 8/14/19 4:05 AM, DD K wrote:
> Hi Brent,
>
> First of all sorry for the late reply. As you've said the way I'm
> doing is not recommended I had to think a bit on the way to get the
> initialization process correctly. In the initialization process the
> file org.opensaml.core.config.Initializer is called to initialize the
> required, but since I'm getting the dependencies using an orbit seems
> the file gets overridden and at last the final dependency's
> initializers would be the only remaining. So to fix this I'm making
> an orbit for each dependency so that they won't get bundled together
> which will not override the file, I've currently done it for only one
> dependency and im planning on doing it to all.
>

Since I don't know OSGi, I don't really understand what any of that
means, what an 'orbit' is, etc.

The InitializationService uses the Java ServiceLoader to find and
execute all the org.opensaml.core.config.Initializer impls that are
declared in the /META-INF/services of the jars present on the runtime
classpath.  Figuring out why that is failing in an OSGi environment and
addressing that would be the appropriate next step.  Maybe for those
familiar with OSGi, the answer is obvious.  I personally just have no
experience with it.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/dev/attachments/20190814/878f8282/attachment.html>