MessageHandlers and SOAP faults

[Brent Putman]

On 6/11/15 9:46 PM, Cantor, Scott wrote:
> On 6/11/15, 8:48 PM, "dev on behalf of Brent Putman" <dev-bounces at shibboleth.net on behalf of putmanb at georgetown.edu> wrote:
>
> Also of course these actions are all -impl classes, so if we really think adding generics to them or actually supplying a type paremeter is right, we can, but I think it just breaks many of the actions on the input side.

Hmm. Still not clear.  The input comes from a MessageDecoder, right? 
That's generic-ed.  A MessageDecoder<SAMLObject> will produce a
SAMLObject.   If somehow what got sent on the wire is not, the throwing
would be there.  I just checked and the decoders are unconditionally
casting, should probably fix that to check and gracefully throw
MessageDecodingException.  But either way that's where I've envisioned
the enforcement of the type that goes into the pipeline.

As you said, the output type is determined by the code, so no real
problem there.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/dev/attachments/20150611/718333c6/attachment.html>