MessageHandlers and SOAP faults
Cantor, Scott
cantor.2 at osu.edu
Sat Jun 13 15:34:08 EDT 2015
On 6/13/15, 3:13 PM, "dev on behalf of Brent Putman" <dev-bounces at shibboleth.net on behalf of putmanb at georgetown.edu> wrote:
>Obviously I agree with the underlying sentiment, but on what basis would the AddSOAPFault - or really the predicate injected into it - really be able to make that determination?
>Vs. the thing that generated the Fault in the first place. Since the predicate
> doesn't actually evaluate the candidate fault message, it can only work an as a general/global flag, all-or-nothing.
It is a global flag.
>However, I was thinking more about what you said re: some actions assuming that the outbound message type was an Envelope. Those might be a problem, esp if we need to compose those with the newer actions for the delegation flow. Can you off-hand give me any examples, or point me to package names, etc?
I'm not finding anything so you're probably right that nothing actually is doing that. But I thought I remembered the encoder implementation being able to handle either a payload or an Envelope as the input message to encode, so I assumed there might be something like that lurking around.
-- Scott
More information about the dev
mailing list