<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 6/20/15 1:51 PM, Cantor, Scott
wrote:<br>
</div>
<blockquote cite="mid:9F6E222D-E235-4B5B-9117-8D22D1E700E0@osu.edu"
type="cite">
<pre wrap="">On 6/19/15, 8:11 PM, "dev on behalf of Brent Putman" <a class="moz-txt-link-rfc2396E" href="mailto:dev-bounces@shibboleth.netonbehalfofputmanb@georgetown.edu"><dev-bounces@shibboleth.net on behalf of putmanb@georgetown.edu></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">And on the AddSOAPFault ProfileAction: In addition to my earlier suggestion that it check for the presence of an outbound Fault already registered per the above, it should probably "emit" any Fault it builds (by Event mapping, etc) using the same mechanism, rather than (unnaturally) sticking it into the MessageContext getMessage().
I think this is a much cleaner and consistent solution. Do you have any objections to that? I think it should be a completely internal change.
</pre>
</blockquote>
<pre wrap="">
No objection, just needs to be fully tested.
</pre>
</blockquote>
<br>
FYI, I just made this change. I've tested it by forcing an NPE
which which causes the class cast exception we were seeing because
of the
<meta http-equiv="content-type" content="text/html;
charset=windows-1252">
AddECPResponseHeaderHandler, and this fixes it. Haven't seen any
other issues except a debug logging issue in EncodeAction, also
fixed.<br>
<br>
<blockquote cite="mid:9F6E222D-E235-4B5B-9117-8D22D1E700E0@osu.edu"
type="cite">
</blockquote>
<br>
</body>
</html>