I don’t think it’s a bug. I think it’s by design and probably for a good reason.
I remember my problem better now; I was getting routing failures like you and looked at the subscriptions. My problem was the MethodName of the Server that was sending in the message. It was using “SomethingElse” and was expecting CCValidateSrv (in your case).
I think the subscription is set up this way to allow multiple Receive Ports to process many different methods (i.e. types of requests). I fixed it by chancing the method name sent by the service.
If you export an Orchestration as a Web Service, the Method Name is the Port Operation Name. If you expose a schema as a web service, I’m not sure where it gets the method name. I bet if you look at the WSDL of the service, you’ll see CCValidateSrv as the method name. Maybe you are not consuming the WSDL correctly?
In my case, the method name was set on the client side.
Oh, you might also want to look at my sample about Untyped Web Services. I don't remember what I did to the Method Name…
Hope this helps.