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

[Brent Putman]

On 8/8/19 12:41 AM, DD K wrote:
> Hi Brent,
>
> I've been able to debug the process and found out that I have got null
> from unmarshallerFactory.getUnmarshaller(element) because there has
> been no unmarshaller registered to unmarshall the element. Can you
> suggest a way to manually register an unmarshaller for the element
> (any resource that i can refer). So my request is as follows:
>

Manually registering an unmarshaller programmatically is possible, but I
would not recommend that for the standard types.  First of all, there's
dozens that you would need to handle all the possible inbound SAML
elements, not just one. Second, you presumably need to respond to the
inbound message, so you'd also need to register all the builders and
marshallers too.

So that's just a non-starter idea.  Need to understand and fix the issue
with library init.

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