<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
<br>
<div class="moz-cite-prefix">On 3/18/16 7:49 AM, Chris Bulcock
wrote:<br>
</div>
<blockquote
cite="mid:1D74086B-248D-420B-81FB-C40BE20BD3AB@ntlworld.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
Is there any documentation on OpenSAML V3 other than that at <a
moz-do-not-send="true"
href="https://wiki.shibboleth.net/confluence/display/OS30"
class=""><a class="moz-txt-link-freetext" href="https://wiki.shibboleth.net/confluence/display/OS30">https://wiki.shibboleth.net/confluence/display/OS30</a></a></blockquote>
<br>
Not, unfortunately not yet. It hasn't been a high priority b/c 1)
external usage of OpenSAML isn't the highest priority for the
Shibboleth project in general, relative to other work, and 2)
probably 90% of it is pretty much the same as v2, modulo changes in
package names, and in some cases class names (but not fundamental
API).<br>
<br>
Upfront the major change is instead of calling:<br>
<br>
DefaultBootstrap.bootstrap()<br>
<br>
you instead call:<br>
<br>
<meta http-equiv="content-type" content="text/html;
charset=windows-1252">
InitializationService.initialize() <br>
<br>
There are some significant changes in classes involved in SAML
metadata resolution (MetadataProvider vs MetadataResolver). Many
people do not use this at all I suspect.<br>
<br>
The biggest change is in the messaging layer: decoders, encoders and
message handling. But again, many people didn't use those
components anyway; it was never really documented for v2, for
example.<br>
<br>
Most people care mostly about the XMLObject providers for the
Java-XML binding layer, and that is virtually identical.<br>
<br>
<blockquote
cite="mid:1D74086B-248D-420B-81FB-C40BE20BD3AB@ntlworld.com"
type="cite">
<div class=""><br class="">
</div>
<div class="">I’m looking for some examples like those provided in
the V2 documentation.<br>
</div>
</blockquote>
<br>
<br>
Much of what is actually in the v2 User Manual is still directly
usable. In fact when we do undertake to document v3 we'll probably
start with cloning that wiki space and then editing.<br>
<br>
Re: the XMLObject provider stuff there, the only big difference is
that: instead of obtaining builders/marshallers/unmarshallers from a
class called Configuration, they are obtained from an instance of
XMLObjectProviderRegistry. For working with the global instance of
that there are some relevant convenience methods available via
XMLObjectProviderRegistrySupport, and some even higher-level
convenience methods in class XMLObjectSupport.<br>
<br>
If you have any specific questions, please feel free to ask here.<br>
<br>
Thanks,<br>
Brent<br>
<br>
<br>
</body>
</html>