OpenSAML 3 unmarshaller为null [英] OpenSAML 3 unmarshaller is null
本文介绍了OpenSAML 3 unmarshaller为null的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!
问题描述
您好我正在将应用移植到opensaml3并遇到以下问题:
Hi i am currently porting an app to opensaml3 and run into the following issue:
InitializationService.initialize();
...
Unmarshaller unmarshaller = Configuration.getUnmarshallerFactory().getUnmarshaller(qName);
我已经通过initialize函数替换了opensaml2和之前的DefaultBootstrap。仍然工厂将我作为编组员返回null。
知道这里出了什么问题吗?
I have replaced the DefaultBootstrap from opensaml2 and previous by the initialize function. Still the factory is returning me null as marshaller. Any idea what is going wrong here?
这是初始化进度的输出:
This is the output from initialize progress:
[main] INFO org.opensaml.core.config.InitializationService - Initializing OpenSAML using the Java Services API
[main] INFO org.opensaml.xmlsec.algorithm.AlgorithmRegistry - Algorithm failed runtime support check, will not be usable: http://www.w3.org/2001/04/xmlenc#ripemd160
[main] INFO org.opensaml.xmlsec.algorithm.AlgorithmRegistry - Algorithm failed runtime support check, will not be usable: http://www.w3.org/2001/04/xmldsig-more#hmac-ripemd160
[main] INFO org.opensaml.xmlsec.algorithm.AlgorithmRegistry - Algorithm failed runtime support check, will not be usable: http://www.w3.org/2001/04/xmldsig-more#rsa-ripemd160
推荐答案
我想你使用的是opensaml v3
所以你应该用这样的XMLObjectProviderRegistrySupport类创建UnmarshallerFactory对象完美
I supose you're using opensaml v3 so You should create the UnmarshallerFactory object with the XMLObjectProviderRegistrySupport class like this it works perfectly
UnmarshallerFactory umFactory=XMLObjectProviderRegistrySupport.getUnmarshallerFactory();
Unmarshaller unmarshaller=umFactory.getUnmarshaller(element);
这篇关于OpenSAML 3 unmarshaller为null的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!
查看全文