XMLObjectSupport.getBuilder() is returning null

[Tom Chiverton]

Thanks DD K - redoing my start up code per you suggestion solved this in 
a better way, and also my marshal problem from the other thread. 
Curiously I think it was changing the Thread's loader, which is 
something I've not had to do when integrating other projects before.

Or it might have been because as Scott suggested, it forced me to bring 
in a whole bunch more .jar's that didn't seem directly required by the code.

I'd love to use v4, but the project's own docs on v4 say "We do *not* 
have significant documentation"[1]. There's much more in the way of 
examples and help out there for v3, and the main Shibboleth application 
which would be the other source of "how to do v4" is too big to easily 
follow.

As far as I know, SAML itself hasn't changed, so I shouldn't be setting 
myself up for anything too nasty :)

Tom

[1]https://wiki.shibboleth.net/confluence/display/OSAML/Home

On 17/06/2021 13:28, Cantor, Scott wrote:
> On 6/17/21, 5:50 AM, "dev on behalf of Tom Chiverton" <dev-bounces at shibboleth.net on behalf of tc at extravision.com> wrote:
>
>>     For the benefit of the future, I couldn't find out what was wrong, so just hacked in a work around in my code :
> You can do what you like, but that's a reliance on a non-API class, and you're using EOL code to begin with, V3 is dead.
>
> The usual cause of issues getting classes registered is missing jars on the classpath. That's how the initializers find their instances to init.
>
> -- Scott
>
>


______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/dev/attachments/20210618/6dc1c9d0/attachment.htm>