That would probably get me over this particular hump, and it would be
the least disrptive, because I have cases where my clients are barfing
because they are getting an actual response, followed by a fault.
On Oct 8, 2008, at 1:38 PM, Daniel Kulp wrote:
That said, I think the PolicyVerificationOutInterceptor should just
log a
warning if something isn't asserted properly. By the time it runs,
stuff is already written out to the client. It's too late to throw a
fault. For the interceptors the can detect that a policy isn't
assertable and they know before things are written out, that
interceptor
should throw an exception imediately, not wait for the verification to
occur. Example: if the password for the X509Token isn't correct or
similar. Instead of not asserting the X509Token policy, throw an
exception.
