<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>FYI, Any followup to comments below should go to the dev list,
not the users list...<br>
</p>
<br>
<div class="moz-cite-prefix">On 3/26/18 1:52 PM, Jürgen Weber wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAFNKvH3eRp+kVkMjVsb=Zv2gFpJ0BJTxJ=WGGWBS2QCEXhHYdw@mail.gmail.com">
<div dir="auto"><span
style="font-family:sans-serif;font-size:12.8px"></span><br
style="font-family:sans-serif;font-size:12.8px">
<br style="font-family:sans-serif;font-size:12.8px">
<font size="2" face="sans-serif">Looks like
-xmltooling-1.3.2-1.jar goes before opensaml-core-3.1.1.jar in
the webapp classpath.</font><span
style="font-family:sans-serif;font-size:12.8px"> </span><br
style="font-family:sans-serif;font-size:12.8px">
<br style="font-family:sans-serif;font-size:12.8px">
<span style="font-family:sans-serif;font-size:12.8px"></span><br
style="font-family:sans-serif;font-size:12.8px">
<br style="font-family:sans-serif;font-size:12.8px">
<font size="2" face="sans-serif">Is there a less drastic way to
solve the problem?</font></div>
</blockquote>
<br>
<br>
Yes. You can't mix OpenSAML 2.x and 3.x. As you have discovered,
you can't have both major versions in your classpath. Pick one
and use that. And you should almost certainly pick 3.x, since 2.x
was EOLed nearly 2 years ago.<br>
<br>
If you're just getting this via spring-ws-security, then check into
what they're doing. If *they* are pulling in both, then that's just
wrong. I don't personally know whether they have upgraded to use
3.x or not.<br>
<br>
FYI, OpenSAML 2.x will be the xmltooling, openws and opensaml2
jars. 3.x will be entirely opensaml-<modulename> jars with
3.x.x version numbers.<br>
</body>
</html>