<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
<div class="moz-cite-prefix">On 1/12/15 4:40 PM, Brent Putman wrote:<br>
</div>
<blockquote cite="mid:54B43F4D.8080709@georgetown.edu" type="cite">
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
<br>
<br>
Now that we've found that, I think we had someone else awhile back
who managed to do the same thing with IdP v2 under some container,
maybe Tomcat. Don't remember how though.<br>
</blockquote>
<br>
For the archives: I found the old similar issue:<br>
<br>
<a class="moz-txt-link-freetext" href="http://marc.info/?t=137987111600002&r=1&w=2">http://marc.info/?t=137987111600002&r=1&w=2</a><br>
<br>
It appears it basically came down to: java.ext.dirs was being
explicitly set, relative to $JAVA_HOME. I infer that during an
upgrade JAVA_HOME switched from pointing at the JDK root to the JRE
root underneath, or vice-versa.<br>
<br>
Personally I don't know why one would bother to explicitly set it to
the place to which it defaults anyway. Best not to muck with it, for
reasons like this. It maybe makes sense if you really do want to
put the ext dir outside of the JDK/JRE directory, etc, and tightly
control the extension jars you are loading. But then you own it.<br>
<br>
</body>
</html>