Sunday 15 July 2012

soap - Losing WCF FaultException details when using binary -



soap - Losing WCF FaultException details when using binary -

i have wcf service next custom binding:

<binding name="binaryhttpbinding" > <binarymessageencoding /> <httptransport maxreceivedmessagesize="2147483647" /> </binding>

(the client has of course of study configuration matches binding). problem client doesn't receive generic faultexception, e.g. "t" not received client, can verify if trace calls. if replace binarymessageencoding textmessageencoding using soap 1.2, fault exceptions come enriched fault detail.

i searched on net , wasn't able find info claim binary message encoding on http not compatible generic wcf fault exceptions. doesn't can command much of binary message encoding - illustration can't set in configuration soap message version (not supported wcf binary encoding). wonder whether scenario supported.

after spending quite hours on trying figure out go wrong, i've made work. 2 reasons failure, none of them obvious.

the fault message class has overridden tostring method did computation. sure unwise set such logic in tostring, guess impact binary serialization? faultexception constructor has optional parameter "actionname" set name of method exception occurred. apparently wcf quite picky can assigned action name leaving blank works. again, guess impact binary serialization , in such unusual way (so discards message fault on client side)?

wcf soap encoding wcf-binding faultexception

No comments:

Post a Comment