wcf-routing

问题 I wanted to create an extension less (file-less if possible) router endpoint via WCF Router Service that has customer user/password security policy. I am getting the following Fault Exception when attempting to route SOAP messages through it: <s:Fault> <faultcode xmlns:a="http://schemas.microsoft.com/net/2005/12/windowscommunicationfoundation/dispatcher">a:InternalServiceFault</faultcode> <faultstring xml:lang="en-US">An unexpected failure occurred. Applications should not attempt to handle

问题 I am using the WCF 4 routing service, and need to configure the service programmatically (as opposed to via config). The examples I have seen of doing so, which are rare, create a MessageFilterTable as follows: var filterTable=new MessageFilterTable<IEnumerable<ServiceEndpoint>>(); But, the generic parameter to that method is supposed to be TFilterData (the type of data you are filtering on)? I have my own custom filter that accepts a string -- can I still create the filter table this way? If

问题 I'm learning about what can be done with the WCF Routing Service. Still at the 'screwing around with it to see what it can do' phase. My understanding of the Routing Service is that when a message comes through, the service will try to pass it on to whichever endpoint appears first in the backup list. If that fails, it will then go on to try the next, and then the next, until either something works or there's nothing left to try. What I would like to do is get access to that failure event so

问题 I have a wcf project that needs to do some routing stuff. One scenario there is, is to do a service versioning. So for example if there is a change or a new service needs to be implemented for a new client on wcf service that is breaking, I will then create a different service endpoint for that to be consumed by the new client. Bu the thing is the old client should still be able to communicate with the older version of the service(That's how service versioning should work right?). To do so, I

问题 I have a simple WCF Client -> Server structure, where the client references the server's WCF service. Authentication is done using X509 certificates. I want to add a simple form of redundancy to my service. meaning- to have several servers running, and have the client use a router that would transparently fail-over to a backup server if the main one is dead. Simple, right? I used the hello world sample code and just changed the app.config file of my router to resemble that of my client. I

问题 The situation is as follows: I have an internal server running some WCF services, and I want them to be accessible from the internet at large. To this end, I have written a routing service that is running on our public facing web-server. This routing service appears to work, however when I attempt to invoke a method, I always get the following error. The message with Action 'http://tempuri.org/IProcessManagementService/ListProcesses' cannot be processed at the receiver, due to a