Hi going back to the policies (as mentioned in the other thread)
The default ChannelReconnectPolicy will retry the call in case of ChannelTerminatedException, CommunicationObjectFaultedException, CommunicationObjectAbortedException, MessageSecurityException or CommunicationException.
However it is exectuted right above the WCF pipeline. In case of most (if not all) of these exceptions the channel will be faulted, so the second try is bound to fail, since the call is executed after Refresh Channel Policy so the second call is bound to fail anyway.
Actually I would go as far as saying that the behavior may be harmful, because since we're eating the first exception we make it harder to find out what the actual reason for the failure is.
Thoughts? Krzysztof -- You received this message because you are subscribed to the Google Groups "Castle Project Development List" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en.
