OpenSAML user discussion

["Cantor, Scott E." <>]

> That's exactly what I'm trying to do: load the PAOS related
> ObjectProviders by using XML file, just like it's done for the other
> ObjectProviders. Now, maybe I'm missing something, but from what I've
> understood, the only way opensaml can be informed about a new config
> file is to modify its bootstrapping process. I know that in my
> application, I could extend the DefaultBootstrap class to add a
> reference to my new file, but I initially thought that it would be
> better to modify the original bootstrapping process. However, since
> you're suggesting otherwise, I could fall back to extending the
> bootstrapping process.

That would be my impression, but Brent and Chad would know better than me.

> In fact, one of the reasons that led me into branching opensaml is
> that I though that if and when you guys would want in incorporate my
> changes, it would be easier to just diff my branch with the official
> one instead of looking at opensaml related changes included in my SP.

The object providers tend to be pretty self-contained.

> Or maybe I'm just getting used with the git way of doing things in
> which branching is quite common.

I don't understand git at all, so maybe you should ignore me.

-- Scott