I'm attempting to leverage the WCF 4.0 Routing Service using IRequestReplyRouter. Most documentation gives the example where a client has knowlege of the endpoint contract it would like to reach, only swapping out the router address/contract for the
endpoint address/contract. Then the Routing Service uses its routing table configuration to figure out the real endpoint address for the message and sends accordingly.
In my architecture, I cannot allow my client to know the ultimate endpoint and contract for where its message is being transmitted. Instead, the client assigns some custom header information to the SOAP envelope (using a Message Contract] that
the Routing Service should use to determine the correct actual endpoint to process the message.
Within Object Browser, I noted that the IRequestReplyRouter contract defines a BeginProcessRequest(...) OperationContract. I believed my solution would be to generate a proxy directly for the Routing Service and call this method explicitly. However,
in generating my proxy I do not find that the BeginProcessRequest method is made available.
Does anybody know why this particular operation does not get exposed to the client via proxy generation? Will I need to create my own service proxy to explicitly - or will this cause other problems?
View Complete Post